Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.


A venv per project is a very sane way. Put them into the ignore file. Hopefully they also could live elsewhere in the tree.


well 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


I think uv's use of a global cache means that having several .venv with the same packages is less of a problem.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: