Description

As posted by @mhvk

Would this still work?

@mhvk Thanks for pointing this out, I honestly had no idea that someone would use tox to create virtualenvs. The answer is a yes but: uv does not include pip itself in virtualenvs it creates (because it makes it redundant), so if you were to run the exact commands you showed in that order, you'd get stopped at

$ pip install ipython
/Users/clm/dev/astropy-project/coordinated/astropy/.tox/test/bin/python: No module named pip

but that's trivially solved by either:

* typing `uv pip` instead of `pip`

* running the awkward (but functional) command `uv pip install pip` between env activation and any further install

is this satisfactory ?

@neutrinoceros - now that this PR is merged, I noticed that my workflow of

tox -e test --develop --notest
source .tox/test/bin/activate
pip install ipython

is indeed broken (as expected). However, your statement that I could just do uv pip install ipython turns out not to be true, since by default uv is not in the path, so I'm stuck with .tox/.tox/bin/uv pip install ipython, which is quite long. There probably is a clever trick to have this work, but I haven't been able to find it. Any suggestions?

Expected behavior

Shouldn't be this hard.

How to Reproduce

See #16963 (comment)

Versions

N/A