A year of uv: pros, cons, and should you migrate
bitecode.dev
A year of uv: pros, cons, and should you migrate
1–10 of 401 posts
Re: A year of uv: pros, cons, and should you migrate
#2Yes. Python tooling has been shit for decades and `uv` is actually good.
Re: A year of uv: pros, cons, and should you migrate
#3uv is overposted as hell, but oh my god I love it so much I understand every single one of these posts. Simple things just work so effectively.
Re: A year of uv: pros, cons, and should you migrate
#4Adding to the article (which I agree with): Lack of `uv pip install --user` has made transitioning our existing python environment a bit more challenging than I'd like, but not a deal breaker.
Re: A year of uv: pros, cons, and should you migrate
#5I think at this point, the only question it remains is how Astral will make money. But if they can package some sort enterprise package index with some security bells and whistles it seems an easy sell into a ton of orgs.
Re: A year of uv: pros, cons, and should you migrate
#6uv is so much better than everything else, I'm just can't afraid they can't keep the team going. Time will tell but I just use uv and ruff in every project now tbh.
Re: A year of uv: pros, cons, and should you migrate
#7> I had a friend who decided to not use uv, because the first time he used it, it was on a 15 years old codebase that had just been migrated to Python 3. It was standing on a pile of never cleaned up pip freeze exports, and uv could not make it work.
This is my only gripe with uv, despite how the author decided to depict it, this really turns into a headache fast as soon as you have ~4-5 in-house packages.
I don't think it's that bad that uv is so unforgiving in those case because it leads to better overall project quality/cohesion, but I wish there was a way to more progressively onboard and downgrade minor version mismatch to warnings.
Re: A year of uv: pros, cons, and should you migrate
#8I thought this was going to be about the UV rays from the sun... But it's another python package manager.
We're running out of names.
Re: A year of uv: pros, cons, and should you migrate
#9Honest question: is uv more reproducible/portable than cramming your Python project into a Docker container? I've used pyenv, pip, venv, and a couple of other things, and they all work fine, at first, in simple scenarios.
Re: A year of uv: pros, cons, and should you migrate
#10I thought this was going to be about the UV rays from the sun... But it's another python package manager. We're running out of names.
I assumed it was going to be about libuv, the event loop library that Node uses.