-
Notifications
You must be signed in to change notification settings - Fork 66
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
PythonCall/juliacall doesn't work in conda environment #25
Comments
Oh, from the PythonCall side I think it already goes wrong during initialization (probably because the python interpreter crashes upon doing
However there is no error/warning message when doing |
|
Your initial problem looks like it's Julia that can't find libpcre, not Python. So I guess the way juliacall is loading libjulia means it can't always link to all the libraries it needs. I take it julia loads OK normally? I wonder if the paths to some dynamic libraries are embedded into the julia executable. Can you locate julia and the libpcre it is using? |
Hi I'm rewriting the package over on the 'rewrite' branch and came across the same problem. I fixed it there. |
hi @cjdoris, I just hit this issue on Windows. I tried to call |
I first noticed this because I tried to
import juliacall
from a plain Python script, running in a conda environment. I then got this error:It looks like it can't load libpcre, which seems weird, because the conda environment should only add to the paths/environment variables, right?
On the other hand, using PythonCall from Julia was working fine, and it was using the Python executable from the environment as well. However, when I switch it to the conda environment explicitly using
ENV["JULIA_PYTHONCALL_EXE"] = "CONDA:..."
it also crashes:I am running on Windows 10, and the conda environment has Python 3.7 installed. However, running
julia
when the environment is activated works fine, and regexes (so libpcre) also work. The only thing I can think of is that there is a mismatch between the libpcre version inside and outside the conda environment. But I'm not still not sure why that only shows up when setting up the Julia runtime from "inside" Python.The text was updated successfully, but these errors were encountered: