You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
add JULIA_PYTHONCALL_EXE=@venv to load python from .venv folder #668
Is your feature request related to a problem? Please describe.
I'd like to disable CondaPkg and use python in manually created .venv
Describe the solution you'd like
add meta config JULIA_PYTHONCALL_EXE=@venv that would load .venv/bin/python or .venv/Scripts/python.exe (on windows).
The folder .venv is at the same folder with (Julia)Project.toml just like .CondaPkg
Additional context
Now we have @CondaPkg (default), and @PyCall, I'd like to add @venv to simplify configuration.
Relatedly, we could also change the env var so that if you pass a relative path, it is interpreted as relative to the current project (instead of the current working directory). This might be breaking though.
For example JULIA_PYTHONCALL_EXE=.venv/bin/python would be equivalent to @venv (on Unix).
Activity
cjdoris commentedon Sep 15, 2025
This is a nice idea!
cjdoris commentedon Sep 15, 2025
Relatedly, we could also change the env var so that if you pass a relative path, it is interpreted as relative to the current project (instead of the current working directory). This might be breaking though.
For example
JULIA_PYTHONCALL_EXE=.venv/bin/pythonwould be equivalent to@venv(on Unix).cjdoris commentedon Sep 15, 2025
Its a slippery slope but we could also add
@uvwhich is like@venvbut also runsuv syncfirst.