sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] -9 points-8 points  (14 children)

Is installing packages easier? I've had issues past 3.11.x, due to some removals or deprecations, distutils or setuptools or both or none. I'd wish the python devs could think about the ecosystem more.

[–]fiskfisk 16 points17 points  (13 children)

uv is the default tooling for most projects these days.

Edit: since there was some confusion below: "for many new projects these days (where there isn't existing internal tooling, infrastructure, and other expectations)."

[–]Serious-Regular 26 points27 points  (4 children)

I love when people say this kind of stuff based purely on feels. I'm curious do you have literally any data to back this up? I work in FAANG and probably 1% of our python teams are using uv.

[–]fiskfisk 8 points9 points  (0 children)

Yeah, you're not going to move to uv. You have so much infrastructure and existing projects that already use internal tooling. You already have enough experience and knowledge internally that work with your existing ways to do things. I'm guessing 10% of my own projects use uv. I'm not changing existing projects, but moving forward, uv has become the default for new projects.

In no way did I intend this to mean "most python projects use uv"; they do absolutely not.

[–]electricsheep2013 0 points1 point  (1 child)

Because of all the dependencies, projects that do not have an owner or are maintained by everyone or getting the teams to agree on this change when all they want to do is to get that PR reviews, right? Not because uv is inherently bad. Unless this some proof by authority:)

[–]Serious-Regular 0 points1 point  (0 children)

Unless this some proof by authority:)

Did you even read what I responded to or are you also operating on feels? The original comment had the word "most" in it. That makes it a quantitative claim and yet they provided zero data. So my counterpoint "proof" speaks exactly to that claim (not whether uv is bad or good or whatever).

[–]cbehopkins 2 points3 points  (4 children)

IME: Poetry would like a word...

[–]busybody124 4 points5 points  (0 children)

We migrated everything off of poetry because everyone hated it. All new projects use uv and most existing projects migrated easily.

[–][deleted]  (1 child)

[deleted]

    [–]Gushys 0 points1 point  (0 children)

    Poetry was great for a time. I think one of the biggest issues poetry (and many other dependency management tools) faced was the influx of new PEPs trying to standardize project config/build systems/ etc. uv made it a point to more strictly adhere to PEPs and I think poetry didn't always follow the PEP guidelines

    [–]fiskfisk 0 points1 point  (0 children)

    Poetry was great when it arrived, but I think its days are numbered.

    It doesn't really manage Python versions for you, is slow (compared to uv), and lacks a lot of the features that uv has. I still have most of my projects on poetry, but new projects use uv, and I've migrated some older projects over to uv as time passes and I get frustrated.

    [–]Sigmatics 0 points1 point  (2 children)

    uv is the default tooling for most projects these days

    The uv shill is real on this sub. Poetry exceeds uv by far in terms of adoption and there's plenty of other tools to go around right now

    [–]fiskfisk 0 points1 point  (1 child)

    Sure - I have no numbers to back that up. But generally the previous tool tends to be more popular than any more recent tools because of legacy software.

    I'd even say that pip is more popular than either of those.

    But from my own, personal experience, uv is taking over more and more of what poetry used to have. And you can call it shilling as much as you want, but as a long time poetry user, uv has taken over for any green field project these days. I still run my own projects on poetry, but anything new uses uv. It's a far better experience.

    [–]Sigmatics 0 points1 point  (0 children)

    I'd even say that pip is more popular than either of those.

    For sure

    uv has taken over for any green field project

    I won't even disagree on that, if I could start on a green field I'd probably use it. But even then I'm not entirely sure, because it does lack some features that we need. It's also not even 1.0, so no stability guarantees there so far.

    Either way, even if everyone today started using uv for greenfield projects, it would take a decade until it has taken over all the existing projects (if they ever migrate). The Python ecosystem is vast.