Pip subcommands are here to ease the transition from the old ecosystem to the new.
Not true, each virtual environment has its own physical copy on disk.
Since creating venvs is usually per project you have many downloads / copies.
See: https://github.com/astral-sh/uv/issues/1495
It's not uncommon to have to download pytorch many times, because some lib may specify one slightly different version than another: https://docs.astral.sh/uv/guides/integration/pytorch/#config...
pytorch causes many headaches in the ecosystem, and a better handling of it is one thing their commercial offering, pyx, wants to fix: https://astral.sh/blog/introducing-pyx
Pip subcommands are here to ease the transition from the old ecosystem to the new.