uv IS the Future of Python Packaging 🐍📦 (www.youtube.com)

submitted 1 year ago by norambna@programming.dev to c/python@programming.dev

44 comments fedilink hide all child comments

via https://mastodon.social/@hynek/113227146595211210

you are viewing a single comment's thread
view the rest of the comments

[-] beeng@discuss.tchncs.de 6 points 1 year ago

Got toml file support yet? Then I'm happy to talk :)

[-] sugar_in_your_tea@sh.itjust.works 5 points 1 year ago

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.

[-] eager_eagle@lemmy.world 4 points 1 year ago* (last edited 1 year ago)

it already has dep groups; e.g.

uv add --optional staging pytest

then

uv sync --extra staging

to install / uninstall packages accordingly.

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.

[-] beeng@discuss.tchncs.de 3 points 1 year ago

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.

[-] SwordInStone@lemmy.world 2 points 1 year ago

yeah, it works with private pypi

[-] beeng@discuss.tchncs.de 3 points 1 year ago

I don't find it in the docs..how to set my PAT?

[-] sugar_in_your_tea@sh.itjust.works 1 points 1 year ago

Oh cool, I'll definitely look into that.

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.