-
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
Respect JULIA_PROJECT environment variable if set #426
Comments
It seems related to https://github.com/JuliaPy/PyJuliaPkg in that a workaround could be to set EDIT: This is not working because of this related bug JuliaPy/pyjuliapkg#15 - PyJuliaPkg will simply delete the entire project folder. There is no workaround for this behaviour currently. |
It seems there is not a single workaround to start JuliaCall in a predefined environment. |
PythonCall already sets up a pseudo Maybe this already existing mechanism could be reused to start juliacall in an existing environment. |
Ignoring |
Thank you for reminding me that both variables need to be set. For me, coming from julia, it is very unintuitive to set two environment variables in order to get an Julia environment to work. My tests where successful, it worked. Thank you. What about translating the JULIA_PROJECT environment variable automatically to those two PYTHON_JULIAPKG environment variables? |
I am using the python package
juliacall
and am surprised to find that it ignoresJULIA_PROJECT
environment variable.Julia documentation about JULIA_PROJECT.
It would be great if this standard variable is respected. Currently juliacall opens a new julia environment
pyjuliapkg
The text was updated successfully, but these errors were encountered: