Putting aside the speed uv has a bunch of features that usually require 2-4 separate tools. These tools are very popular but not very well liked. The fact these tools are so popular proves that pip is not sufficient for many use cases. Other languages have a single tool (e.g. cargo) that are very well liked.

If you do multi stage builds (example here) it is slightly easier to use venvs.

If you use the global environment you need to hardcode the path to global packages. This path can change when base images are upgraded.

Sure, but in the case where you upgrade python and it affects python packages it would affect global packages and a venv in the same way.

upgrading your base image won’t affect your python packages

Surely if upgrading python will affect your global python packages it will also affect your venv python packages?

you can use multi stage builds to create drastically smaller final images

This can also be done without using venv’s, you just need to copy them to the location where global packages are installed.

I don’t think they have anything to do with each other, it looks like prefix.dev uses conda packages.

Yeah it is, eventually they want UV to have feature parity with rye and rye will basically just be a pointer to UV

Early on uv was only trying to replace pip. This latest update is a big step towards becoming a poetry (and pyenv/pipx) replacement too.

This actually sounds really promising!

• They are teaming up with an existing python package manger written in rust.
• These are the people who make/made ruff, probably the most useful and fast python linter.
• you basically get pip from a single binary.
• they plan to have cargo/poetry like functionality in the future.

Edit: here is a blog post from the creator of rye talking about rye and UV: https://lucumr.pocoo.org/2024/2/15/rye-grows-with-uv/