35
uv IS the Future of Python Packaging 🐍📦 (www.youtube.com)
submitted 2 months ago by norambna@programming.dev to c/python@programming.dev
43 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
[-] dinckelman@lemmy.world 27 points 2 months ago

It’s a really bold claim. Every time a new package manager and/or dependency resolver comes around, we have the exact same headline

[-] fnrir@lemmy.world 10 points 2 months ago
[-] TriflingToad@lemmy.world 3 points 2 months ago

I think of this literally every time I have any issue

[-] BitSound@lemmy.world 7 points 2 months ago

It is a bold claim, but based on their success with ruff, I'm optimistic that it might pan out.

[-] dinckelman@lemmy.world 3 points 2 months ago

I do enjoy ruff a lot, but only time will tell

[-] solrize@lemmy.world 5 points 2 months ago

There are 14 competing standards...

[-] ALERT@sh.itjust.works 1 points 2 months ago

have there been a lot of them?

[-] monogram@feddit.nl 10 points 2 months ago

pipx, poetry, pipsi, fades, pae, pactivate, pyenv, virtualenv, pipenv

Let’s hope this next one will be the true standard.

[-] onlinepersona@programming.dev 7 points 2 months ago

pyenv, virtualenv, pipenv, aren't package managers... they are virtual environment managers / creators and use pip for package management.

Anti Commercial-AI license

[-] sugar_in_your_tea@sh.itjust.works 4 points 2 months ago

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.

[-] dallen@programming.dev 7 points 2 months ago

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.

[-] sugar_in_your_tea@sh.itjust.works 2 points 2 months ago

Yeah, it certainly looks nice, but my problems are:

  • everything runs in a docker container locally, so I don't think the caching is going to be a huge win
  • we have a half-dozen teams and a dozen repositories or so, across three time zones, so big changes require a fair amount of effort
  • we just got through porting to poetry to split into dependency groups, and going back to not having that is a tough sell

So for me, it needs to at least have feature parity w/ poetry to seriously consider.

[-] monogram@feddit.nl 3 points 2 months ago

You should be using dockers cache mounts

https://docs.docker.com/build/cache/optimize/#use-cache-mounts

[-] sugar_in_your_tea@sh.itjust.works 3 points 2 months ago

Good call. We have some other tech debt related to our docker usage, so I'll add this to the list.

[-] eager_eagle@lemmy.world 3 points 2 months ago* (last edited 2 months ago)

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.

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

I'm not really worried about the migration work, from what I can tell it's basically just moving a few things around. I'm more worried about losing features the team likes largely for performance reasons.

Our primary use cases are:

  • dev tools - standardize versions of tools like black, pylint, etc; not necessary if we move to ruff, we'll just standardize on a version of that (like we do with poetry today)
  • tests - extra deps for CI/CD for things like coverage reports

I like the syntax poetry has, but I'd be willing to use something else, like in PEP 735.

One thing we also need is a way to define additional package repos since we use an internal repo. I didn't see that called out in the PEP, and I haven't looked at uv enough to know what their plan is, but this issue seems to be intended to fix it. We specify a specific repo for a handful of packages in each project, and we need that to work as well.

I'm currently looking to use ruff to replace some of our dev tools, and I'll look back at uv in another release or two to see what the progress is on our blockers.

this post was submitted on 30 Sep 2024
35 points (83.0% liked)

Python

6478 readers
1 users here now

Welcome to the Python community on the programming.dev Lemmy instance!

📅 Events

PastNovember 2023

October 2023

July 2023

August 2023

September 2023

🐍 Python project:
💓 Python Community:
✨ Python Ecosystem:
🌌 Fediverse
Communities
Projects
Feeds

founded 2 years ago
MODERATORS
erlingur@programming.dev
jnovinger@programming.dev
norambna@programming.dev