News for hackers. Stuff that matters.

A comment on Uv is the best thing to happen to the Python ecosystem in a decade. Parent comment

Re:Uv is the best thing to happen to the Python ecosystem in... by gempir on Thursday October 30, 2025 @03:16AM (#45757236)
This is easier to do with uv than it is with pip.

You can create venvs wherever you please and then just install stuff into them. Nobody forces the project onto you, at work we don't even use the .toml yet because it's relatively new, we still use a python_requirements.txt and install into a venv that is global to the system.

[ Parent | on HN ]
Re:Uv is the best thing to happen to the Python ecosystem in... by zelphirkalt on Thursday October 30, 2025 @05:10AM (#45757871)
Way to go to create non-reproducible results. Basically, nothing production ready is rolling out of that one.
[ Parent | on HN ]
Re:Uv is the best thing to happen to the Python ecosystem in... by gempir on Thursday October 30, 2025 @05:18AM (#45757917)
This is what the OP wanted. I don't agree to do it this way.

At work for us we use uv pip freeze to generate a more strict requirements file.

[ Parent | on HN ]
Re:Uv is the best thing to happen to the Python ecosystem in... by zelphirkalt on Thursday October 30, 2025 @05:50AM (#45758123)
What I was referring to is:

> [...] at work we don't even use the .toml yet because it's relatively new, we still use a python_requirements.txt and install into a venv that is global to the system.

Unless your `python_requirements.txt` also carries checksums, like uv's lock files or poetry's lock files, that is. Though of course things get spicy and non-reproducible again, if you have then multiple projects/services, each with their own `python_requirements.txt`, all installing into that same global venv ...

[ Parent | on HN ]