Last month, I wrote Python’s UV tool is actually pretty good about Astral’s new Python package installer and resolver uv, and this is a follow-up post.
Since last month, I have added uv to over a dozen projects, and I recently learned that you could skip the venv step for projects that use containers or CI where the environment is already isolated.
I mistakenly thought uv required a virtual environment (aka venv), but Josh Thomas recently pointed out that it’s unnecessary.
I have a pip-tools wrapper thing that now optionally uses uv instead. Aside from doing the pip-tools things faster, the main advantage I’ve found, and what really motivated me to support and recommend uv with it, is that uv creates new venvs MUCH faster than python’s venv module, which is really annoyingly slow for that operation.
@Andy @xantoxis
The issue with uv is the same
biggest issuethat Python faces, maintenance costs.Python coders are not Rust coders. Which is quite the head scratcher.
Learning Rust techstack creates an enormous
barrier to entrywhen it comes to adopting, uv.uv main advantage is not speed, it’s the override for resolving dependency hell
If it didn’t bring something more to the table, besides speed, no one would care
I’m literally saying its speed in certain operations makes an appreciable difference in my workflows, especially when operating on tens of venvs at a time. I don’t know why you want to fight me on my own experience.
I’m not telling anyone who doesn’t want to use uv to do so. Someone asked about motivation, and I shared mine.