-
Notifications
You must be signed in to change notification settings - Fork 101
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
SystemError: initialization of _heapq did not return an extension module #150
Comments
Have exactly the same error: |
I have a similar error but it happens in
SystemError: initialization of _heapq did not return an extension module
|
I have the same problem: julia.Julia(debug = True) |
I have a similar issue on my conda python, but not the homebrew python. It may be because JuliaCall fails to detect if (anaconda/miniconda) python has been initialized. I got the following from my miniconda python
I got the following from my homebrew python
UPDATE: The following code works in miniconda python
And it seems that PyCall already loads in process symbols JuliaPy/PyCall.jl#293 |
I am having the same issue with miniconda. I am also getting the same outputs as in #175 (comment) Any ideas why it cannot detect if python has been initialized? |
Hmm... I thought I fixed #175 by this commit. Does it happen with PyJulia master as well? I remember it happened with Julia 0.6 when the precompilation failed. |
Yes I am using the master and Julia 1.0. I deleted the |
Julia 1.0 with miniconda is not supported ATM so it is supposed to print some informative error message. Are you using Linux? If you use miniconda in Linux, |
I am using Mac but it actually works with |
Good that it works! BTW, in your comment you are mentioning you tried
doesn't show libpython? Do you actually have Additionally, can you run the following in miniconda from julia.find_libpython import find_libpython, linked_libpython
linked_libpython() # what does it return?
find_libpython() # what does it return? I thought macOS didn't need
Yeah I know... But I can't do anything now. 😿 |
Sorry, I meant I have tried your commands.
Thanks for the quick responses by the way :) |
You are welcome :) And thanks for trying the commands. Good to figure out that |
It turned out macOS can have statically linked Python when it's installed via conda: JuliaPy#150 (comment) So it seems `linked_libpython` (which calls `libdl`) is the only way to reliably detect if the Python executable is statically linked or not. Since cd2e408 implements it for Windows as well, we can simplify core.py.
It turned out macOS can have statically linked Python when it's installed via conda: JuliaPy#150 (comment) So it seems `linked_libpython` (which calls `libdl`) is the only way to reliably detect if the Python executable is statically linked or not. Since cd2e408 implements it for Windows as well, we can simplify core.py a lot by relying on `linked_libpython`.
It turned out macOS can have statically linked Python when it's installed via conda: JuliaPy#150 (comment) So it seems `linked_libpython` (which calls `libdl`) is the only way to reliably detect if the Python executable is statically linked or not. Since cd2e408 implements it for Windows as well, we can now rely on `linked_libpython` everywhere which simplifies core.py.
It turned out macOS can have statically linked Python when it's installed via conda: #150 (comment) So it seems `linked_libpython` (which calls `libdl`) is the only way to reliably detect if the Python executable is statically linked or not. Since cd2e408 implements it for Windows as well, we can now rely on `linked_libpython` everywhere which simplifies core.py.
Removing OS: Ubuntu 16.04 (running inside a Docker container) |
I'm experiencing the same error mentioned by @sirgogo in #88 .
I'm running Arch Linux and using the following versions:
Any advice is appreciated!
Thanks,
Oliver
The text was updated successfully, but these errors were encountered: