4 ms·
rye's habit of insisting on creating a .venv per project is a deal-breaker. I don't want .venvs spread all over my projects eating into space (made worse by the
by noisy_boy 2y ago
rye's habit of insisting on creating a .venv per project is a deal-breaker. I don't want .venvs spread all over my projects eating into space (made worse by the ml/LLM related mega packages). It should atleast respect activated venvs.
- nine_k 2y agoA venv per project is a very sane way. Put them into the ignore file. Hopefully they also could live elsewhere in the tree.
- VeejayRampay 2y agowell that's good for you, but you're in the minority and rye will end up being a standard anyway, just like uv and ruff, because they're just so much better than the alternatives
- fastasucan 2y agoI think uv's use of a global cache means that having several .venv with the same packages is less of a problem.