-
Notifications
You must be signed in to change notification settings - Fork 67
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
"Python exited unexpectedly" when using external conda environment #85
Comments
Thanks. The issue is that both PythonCall and PyCall act like they "own" the Python interpreter instance, which is a bug. I'm rewriting the initialisation part of PythonCall soon so I'll make sure this bug is fixed as part of that. |
I believe this is fixed now on the master branch. Can you check please? |
I checked from the python side and it works without any problem. (Just a note, it is probably necessary to run Pkg.resolve() inside the julia_env folder in the custom conda environment after reinstalling the python package if the dependencies change.) For the julia side, it still exits with this warning. I assume updating the package using
|
Aha I missed a case, I can make that warning go away. Thanks for checking. Yeah the resolve thing you mentioned only affects people running the development version. |
Pretty sure this is correct on |
Thanks! Confirmed this is fixed. |
Thank you for this great package!
I've come across this warning after configuring PythonCall to use the PyCall environment. It does not seem to interfere with usage though. When using "Ctrl + D" for exit this results in segmentation fault but still exits.
MWE after starting julia:
The text was updated successfully, but these errors were encountered: