most @import fail in virtualenv about pycall.jl HOT 2 CLOSED

After further inspection, it seems to me that the @windows_only handling of exec_prefix is the culprit. In a virtualenv, exec_prefix points to the virtualenv's root (in my case /home/beyer/sci-env3-dyn) and thus, if the @windows_only check is removed, sys.path is exactly the same within julia as it is within python itself, allowing me to @pyimport all the python modules I installed in the virtualenv.

Regarding the empty string value of sys.executable, this seems to be the expected behaviour when sys.argv[0] is empty, and unrelated to this issue anyways.

So the question is: why was this block made @windows_only in the first place?

• It has been introduced by 0fad204, which only talks about windows.
• It's using sys.exec_prefix (through distutils.sysconfig.EXEC_PREFIX) which, according to the documentation, takes care of virtualenvs and is not OS-specific.
• It's later been expanded by 62cf664, which, again, doesn't seem windows-specific to me.

Am I missing anything, or can we just remove that @windows_only check and have things working correctly with virtualenvs?

from pycall.jl.

Yes, making that @windows_only was probably an excess of caution. Probably we should set PYTHONHOME to prefix:exec_prefix, though?

from pycall.jl.