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 ...
They have a --dev shorthand for dev dependencies, but it seems the dependency group PEP is not final, so there isn’t a standardized way of doing this yet.
And honestly, the one I need more is a test group for CI, for things like coverage reporting and whatnot. If I can get that and if having multiple package indexes works properly (i.e. it can check my private repo first, and then pypi), I can probably port our projects to uv, at which point it’s an internal discussion instead of a technical one.
Got toml file support yet? Then I’m happy to talk :)
Looks like it has basic support:
required-python = "..."dependencies = [ ... ]Once it gets dependency groups, I’ll try it out. I’m currently using
poetry, which works, but I’m always interested in better perf.it already has dep groups; e.g.
uv add --optional staging pytestthen
uv sync --extra stagingto install / uninstall packages accordingly.
They have a
--devshorthand for dev dependencies, but it seems the dependency group PEP is not final, so there isn’t a standardized way of doing this yet.Private PyPI too?
We’re coming from poetry but it’s slow and needs its own .venv, so a UV binary would be very nice.
yeah, it works with private pypi
I don’t find it in the docs…how to set my PAT?
Oh cool, I’ll definitely look into that.
And honestly, the one I need more is a
testgroup for CI, for things like coverage reporting and whatnot. If I can get that and if having multiple package indexes works properly (i.e. it can check my private repo first, and then pypi), I can probably port our projects to uv, at which point it’s an internal discussion instead of a technical one.they do, just use project management commands like
uv+ {add,remove,sync,lock,run}