Comment by hmartin
6 hours ago
Thank god it has opinionated quirks that old timers dislike.
Otherwise we'd still be stuck in the complete dumpster fire that was the python packaging/venv we had for the previous 20 years.
6 hours ago
Thank god it has opinionated quirks that old timers dislike.
Otherwise we'd still be stuck in the complete dumpster fire that was the python packaging/venv we had for the previous 20 years.
True, before UV the only way to package python was a container.
Yup, I ended up learning docker because Python packaging was such a dumpster fire.
I'll never forget the day I discovered that pip didn't do any dependency resolution. You had one job, and yet...
Until uv, I used docker to run python projects locally. Got so fed up with venvs and versions and slowness and lack of wheels and spending so much time mucking around with it when cloning or updating a repo.
Uv hasn't fixed all issues, but made it far less painful.
Old timer here: uv is not the first opinionated tool to manage Python packaging. It is build learning from other tools right and wrongs. I now use uv for everything because its quirks are less disruptive than quirks from previous tools that I also tried and disliked for being a bit too much for a very small gain.
What you call "dumpster fire", I call "steps towards uv", maybe even better tools in the future.