It's been six months since I asked whether uv is the future of Python packaging: https://youtu.be/_FdjW47Au30With uv 0.3.0, the answer is in and I'll tell yo...
I’ve been mostly a poetry guy but have tested out uv a bit lately. Two main advantages I see are being able to install Python (I relied on pyenv before) and it’s waaay faster at solving/installing dependencies.
It’s a really bold claim. Every time a new package manager and/or dependency resolver comes around, we have the exact same headline
Relevant XKCD
There are 14 competing standards…
It is a bold claim, but based on their success with ruff, I’m optimistic that it might pan out.
I do enjoy ruff a lot, but only time will tell
have there been a lot of them?
pipx, poetry, pipsi, fades, pae, pactivate, pyenv, virtualenv, pipenv
Let’s hope this next one will be the true standard.
pyenv, virtualenv, pipenv, aren’t package managers… they are virtual environment managers / creators and use pip for package management.
Anti Commercial-AI license
We’re using poetry and it solves our problems. I’ll have to look into uv, but I don’t feel in any rush to switch away from poetry.
I’ve been mostly a poetry guy but have tested out uv a bit lately. Two main advantages I see are being able to install Python (I relied on pyenv before) and it’s waaay faster at solving/installing dependencies.
Yeah, it certainly looks nice, but my problems are:
So for me, it needs to at least have feature parity w/ poetry to seriously consider.
You should be using dockers cache mounts
https://docs.docker.com/build/cache/optimize/#use-cache-mounts
uv is still faster with a cold cache
and uv does have dep groups
about the second problem, there’s an issue open on writing a migration guide, but migrating manually is not too difficult.