-
Notifications
You must be signed in to change notification settings - Fork 102
A script for reproducing the initialization error #175
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Of course, @stevengj already knew the answer #92 (comment) |
Using conda makes difference since: $ ldd ~/miniconda3/bin/python | grep libpython
$ ldd /usr/bin/python | grep libpython
libpython3.6m.so.1.0 => /usr/lib/libpython3.6m.so.1.0 (0x00007ff5b75ab000) |
tkf
added a commit
to tkf/pyjulia
that referenced
this issue
Aug 22, 2018
tkf
added a commit
to tkf/pyjulia
that referenced
this issue
Aug 22, 2018
tkf
added a commit
to tkf/pyjulia
that referenced
this issue
Aug 28, 2018
tkf
added a commit
to tkf/pyjulia
that referenced
this issue
Aug 29, 2018
tkf
added a commit
to tkf/pyjulia
that referenced
this issue
Aug 29, 2018
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
I think I found a reproducible script to get the error I saw sometimes. Confusingly, the key to get the error was to execute
using PyCall
in Julia to invoke precompilation. Before running this script, remove~/.juliarc.jl
if you have PyCall-related configuration.:This script produces:
If I don't run
using PyCall
beforepython -c 'import julia; julia.Julia()'
, I don't see this error. Above error also vanishes if I don't includejulia.Julia()
so I think it's pyjulia specific and notvirtualenvwrapper
even though it is mentioned in the error message above. This error is also reported #150 andError processing line 1 of
points to another Python library. See below also.A very confusing effect is that, if I use Python environment created by conda for configuring PyCall, i.e., if I do
then I get another error
in 779808b and
in the current head e617ad9. (Note that everything can be reproducible in the current head except the above
Exception 'InitError' occurred while calling julia code
part). The last exception was actually a "bug" introduced by my patch #162 (which didn't manifest unless you miss-configured pyjulia/PyCall...). pyjulia won't work anyway but the error message should be clearer. I'll fix it.The text was updated successfully, but these errors were encountered: