-
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
segfault on Python 3.5 #66
Comments
Fixed by re-installing. Still no idea what was causing the problem. I'm still getting segfaults if I do |
|
Yes, PyCall has been built successfully. I haven't been able to reproduce that error since I reinstalled (but PyCall was definitely built when it was thrown), so I really have no idea what happened. Ok, I am still rather confused but at least now I can consistently reproduce the errors I am getting. I'm pretty sure these errors are only occurring for packages which use PyCall but I'm not certain (it's certainly not every package). I get the following error
However, if I am in the home directory of pyjulia I instead get
|
@Keno, this seems like a conflict between your "fake-julia" precompilation trick and precompilation of packages with PyCall. Does precompilation using |
I'm experiencing what I think is the same issue, using Julia v0.0.5 ( binary release), Python 2.7.6, Ubuntu 14.04
|
Also seeing such an error, on multiple machines, Linux and OSX: The minimal python test case looks like this. The hack makes no difference, in my private copy of the bugfixed package I get the same segmentation fault:
|
I had the same issue on Julia v0.5.0, (binary release), Python 2.7.6, Ubuntu 14.04, but a |
Sorry all. I had completely forgotten about this and have recently reposted it as #92. I'll close this in favor of that one. |
I get the following segfault when I do
j = julia.Julia()
on Python 3.5.My PyCall package has been successfully compiled for Python 3.5.
The text was updated successfully, but these errors were encountered: