Earlier quoted context omitted.
That's my main use case not-yet-supported by uv. It should not be too difficult to add a feature or wrapper to uv so that it works like pew/virtualenvwrapper. E.g. calling that wrapper uvv, something like 1. uvv new --python=... ...# venvs stored in a central location 2. uvv workon # now you are in the virtualenv 3. deactive # now you get out of the virtualenv You could imagine additional features such as keeping a l…
So this is probably just me not understanding your use case, but surely this is a nearly identical workflow? 1. uv init # venv stored in folder-name/.venv 2. cd # running stuff with uv run will automatically pick up the venv 3. cd .. # now you get out of the virtualenv
The UX improvement would be to have a centralized managemend of the venv (centralized location, ability to list/rm/etc. from name instead of from path).