News for hackers. Stuff that matters.

A comment on Free-threaded CPython is ready to experiment with. Parent comment

Re:Free-threaded CPython is ready to experiment with by noisy_boy on Friday July 12, 2024 @09:11PM (#40950952)
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.
[ Parent | on HN ]
Re:Free-threaded CPython is ready to experiment with by nine_k on Friday July 12, 2024 @11:10PM (#40951467)
A venv per project is a very sane way. Put them into the ignore file. Hopefully they also could live elsewhere in the tree.
[ Parent | on HN ]
Re:Free-threaded CPython is ready to experiment with by VeejayRampay on Saturday July 13, 2024 @07:10AM (#40953359)
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
[ Parent | on HN ]
Re:Free-threaded CPython is ready to experiment with by fastasucan on Tuesday July 16, 2024 @05:06AM (#40974759)
I think uv's use of a global cache means that having several .venv with the same packages is less of a problem.
[ Parent | on HN ]