PyCall doesn't work with Enthought Canopy / EPD

[celestrist]

When I type @pyimport math, I get this error message:

ERROR: could not load module /Library/Frameworks/Python.framework/Versions/Current/bin/python: dlopen(/Library/Frameworks/Python.framework/Versions/Current/bin/python.dylib, 9): image not found
 in pyinitialize at /Users/Celestrist/.julia/PyCall/src/PyCall.jl:365
 in pyimport at /Users/Celestrist/.julia/PyCall/src/PyCall.jl:105

Any idea what happens?

[stevengj]

Which version of Python are you using? The one that comes with OSX, Anaconda, or Enthought?

[celestrist]

I am using Enthought Canopy python 2.7

Sent from my iPad

On 16 Sep, 2013, at 11:56 PM, "Steven G. Johnson" notifications@github.com wrote:

Which version of Python are you using? The one that comes with OSX, Anaconda, or Enthought?

—
Reply to this email directly or view it on GitHub.

[malmaud]

I too was having continual problems with pycall and Canopy. I just ended up switching to anaconda, which worked without incident.

[stevengj]

See also JuliaLang/IJulia.jl#86

[pluskid]

Same here:

ERROR: could not load module python: dlopen(python.dylib, 9): image not found
 in pyinitialize at /Users/chiyuan/.julia/PyCall/src/PyCall.jl:372
 in pyimport at /Users/chiyuan/.julia/PyCall/src/PyCall.jl:105

Everything looks fine when I switch to the system built-in Python.
Is there any workaround by explicitly specifying some PATH?

[pluskid]

I just found that calling

pyinitialize("python2.7")

before using any PyCall functions looks good. I guess making a symlink from libpython2.7.dylib to libpython.dylib in Canopy's distribution will also work.

[stevengj]

Are you sure that python2.7 is Canopy's Python executable? Type which python2.7 at the shell prompt....it might be the /usr/bin/python2.7 that ships with MacOS.

(The basic problem here seemsto be that Canopy's python does not seem to set up its sysutils.distconfig variables correctly.)

[pluskid]

@stevengj You are right. I superficially thought that the error was caused by libpython2.7.dylib as the error message was not being able to find python.dylib. It seems it turns out to be what you said -- I switched to the system python when explicitly initialize with python2.7. :(

[thoth291]

I have tried loading pythonxy version of python (PYTHON were set properly). Had the same issues during initialization under Windows 7 x64 (Julia Version 0.3.1 x86_64-w64-mingw32). Would be nice to get fixed as well.

in pyinitialize at C:\Users....julia\v0.3\PyCall\src\PyCall.jl:457
in pyinitialize at C:\Users....julia\v0.3\PyCall\src\PyCall.jl:451

[stevengj]

@dpinte, any thoughts?

[dpinte]

@stevengj I started looking into the initialization code just after EuroScipy.

On Windows, the issue seems to be with the initialization code in PyCall. From what I remember, the initialization will fail with any venv (on Python 3) or virtualenv setup or the venv backport that Canopy uses on Python 2.7. I'll try to dig a bit more into the issue and share my notes to make it work on Windows. The fix was not trivial though.

On my OSX install, it worked like a charm without any changes (which is surprizing looking at what I've seen for Windows). I am using Canopy 1.4.1 and have the Canopy Python registered on my .profile.

[stevengj]

Thank, I appreciate any tips. The overriding goal here is to initialize Python correctly given only the name of the python executable (or the full path if the executable is not in the PATH), since that is the only thing that an end user can reasonably be expected to know. It seems insane how hard this turns out to be to accomplish in a portable way.