17 ms·
So this is probably just me not understanding your use case, but surely this is a nearly identical workflow? 1. uv init <folder-name> # venv stored in folder-n
by Doxin 2y ago
So this is probably just me not understanding your use case, but surely this is a nearly identical workflow?
1. uv init <folder-name> # venv stored in folder-name/.venv
2. cd <folder-name> # running stuff with uv run will automatically pick up the venv
3. cd .. # now you get out of the virtualenv
- cdavid 2y agoYes, that's what I do today. 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).