Re:Production-ready Docker Containers with uv
by ssahoo on Wednesday September 04, 2024 @11:36AM
(#41447011)
What is the benefit of using uv over pip if it's inside a container? Pythons virtual environment is not enough?
[ Parent
| on HN ]
Re:Production-ready Docker Containers with uv
by hynek on Wednesday September 04, 2024 @12:47PM
(#41447840)
It’s much, much faster both in creating virtualenvs and installing the dependencies. And if you use lock/sync, you get a cross-platform lockfile that you only got with PDM and Poetry before – no more requirements.txt (but it supports it too).
Re:Production-ready Docker Containers with uv
by greener_grass on Thursday September 05, 2024 @06:12AM
(#41455212)
Why was UV created when we already have PDM and Poetry?
Genuine question, we are drowning in options here!
Re:Production-ready Docker Containers with uv
by hynek on Thursday September 05, 2024 @12:09PM
(#41457953)
Both PDM and Poetry are a) 90% solutions that only cover what their respective authors need (and this is indeed what Python is drowning in) and b) written in Python which makes them slow and somewhat janky since Python installations and virtualenvs tend to break (lol Homebrew).
I personally love PDM, and PDM is in the process of adopting uv’s lower-leveln functionality to install/resolve packages, but I can see how having a single binary for bootstrapping a whole dev environment is really nice.
In the end, uv’s biggest upside is that it has several people work 8h / day on it and one would be surprised how much can be achieved in such amount of time.