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
Hi there, thanks for this tool, it's been a pleasure to use!
I have a feature request that I think would be useful. In conda you can have globally accessible envs and activate them anywhere with conda activate env_name. These envs simply live in ~/.miniconda. I really like this feature because I often find myself keeping an old venv while working on a feature that requires a new dependency and creating a new venv for that. I think it would be nice to be able to run uv activate env_name from anywhere instead of source path/to/project/.venv/bin/activate. This would likely require an option when creating a venv, e.g -n <env_name> which would then automatically store the env somewhere sensible under that name and allow for uv activate env_name
This definitely may be out of scope for uv, so feel free to ignore it 😄
The text was updated successfully, but these errors were encountered:
Hi there, thanks for this tool, it's been a pleasure to use!
I have a feature request that I think would be useful. In conda you can have globally accessible envs and activate them anywhere with
conda activate env_name
. These envs simply live in~/.miniconda
. I really like this feature because I often find myself keeping an old venv while working on a feature that requires a new dependency and creating a new venv for that. I think it would be nice to be able to runuv activate env_name
from anywhere instead ofsource path/to/project/.venv/bin/activate
. This would likely require an option when creating a venv, e.g-n <env_name>
which would then automatically store the env somewhere sensible under that name and allow foruv activate env_name
This definitely may be out of scope for uv, so feel free to ignore it 😄
The text was updated successfully, but these errors were encountered: