-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release 0.6] stack overflow when using pyjulia #22866
Comments
update: based on: #22320 , https://stackoverflow.com/a/20744680
Works like un-holy magic |
So one option here is to run the initialization on a different thread (for which we control the stack size). That'd require some rejiggering of the embedding API (to register an additional thread as being managed/switching the main thread), but would probably be an easier backport to 0.6. @vtjnash thoughts? |
Fixed on master. I think the workaround posted above is acceptable for v0.6? |
People keep running into this and asking them to download the VS dev tools and change their python executable is not an acceptable solution. We should fix this on 0.6 one way or another. Adding some features to the embedding API to be able to do the initialization on a different thread doesn't seem so hard. |
Another option would be automatically stack switch if we detect that the stack isn't large enough. |
I had same issue but with Python 3.5 (Anaconda distribution.) I followed steps of TsurHerman but it just changed the type of error thrown. Now I get:
Sorry if this is comment is missing any information. This is the first time I have submitted a bug report to an open source project. Let me know if I can provide any more useful info. |
Looks like somewhere along the line it accidentally picked up python 2.7. Make sure you have the latest versions of PyCall and pyjulia which have some fixes that might help. |
Thanks. Reinstalled PyCall and pyjulia and seems to be working now. I think I had recent (if not latest versions) but it might have been that I didn't set up the correct environment variable ENV["PYTHON"] in Julia before installing PyCall. Did that this time so could have been what did the trick. |
fix JuliaLang#22866 [release-0.6 only]
Seem closed by #23255 |
I have Julia 0.6 and Python 3.5.2. I am still getting this error :( |
Do you have julia 0.6.2? |
No, julia 0.6.0
|
I think the patch that fixed this is only available in 0.6.2. You can download it from https://julialang.org/downloads/. |
probably related to #22320
On windows:
After upgrading to Julia 0.6 and Python 3.6
when I call
julia.Julia() from Python
I get exception:
Any workarounds or steps to resolve this issue would be appreciated.
The text was updated successfully, but these errors were encountered: