Skip to content
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

Miniconda style virtual env managment #6501

Closed
sash-a opened this issue Aug 23, 2024 · 1 comment
Closed

Miniconda style virtual env managment #6501

sash-a opened this issue Aug 23, 2024 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@sash-a
Copy link

sash-a commented Aug 23, 2024

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 😄

@zanieb
Copy link
Member

zanieb commented Aug 23, 2024

Hi! I think this is a duplicate of #1495

@zanieb zanieb closed this as not planned Won't fix, can't repro, duplicate, stale Aug 23, 2024
@zanieb zanieb added the duplicate This issue or pull request already exists label Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants