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
For various reasons, I don't keep my .venv directory in the same directory as the project (as seems to be increasingly a convention and is default in uv currently).
I'm coming from using virtualenvwrapper where I could configure a WORKON_HOME as the location for the envs.
I can replicate this for each venv with something like this:
uv venv ~/.envs/$(basename "$PWD")
However I think a limitation of this is that uv isn't able to automatically activate the venv when running e.g uv sync.
It would be really nice to have the location (prefix to a directory containing them, defaulting to .) of the envs exposed in ~/.config/uv/uv.toml. This, ideally, would then be respected in other commands like uv sync.
The text was updated successfully, but these errors were encountered:
For various reasons, I don't keep my
.venv
directory in the same directory as the project (as seems to be increasingly a convention and is default inuv
currently).I'm coming from using
virtualenvwrapper
where I could configure aWORKON_HOME
as the location for the envs.I can replicate this for each venv with something like this:
uv venv ~/.envs/$(basename "$PWD")
However I think a limitation of this is that
uv
isn't able to automatically activate the venv when running e.guv sync
.It would be really nice to have the location (prefix to a directory containing them, defaulting to
.
) of the envs exposed in~/.config/uv/uv.toml
. This, ideally, would then be respected in other commands likeuv sync
.The text was updated successfully, but these errors were encountered: