Yeah, I find that I like to use uv for one thing, quickly/efficiently getting a Python into a new venv for some project. A la:

  uv venv ~/.venvs/my_new_project --python 3.13
  source ~/.venvs/my_new_project/bin/activate
  python3 -m ensurepip --upgrade
  cp -r /path/from/source/* .
  python3 -m pip install -r requirements.txt

So here uv installs the Python version wanted. But it's just a venv. And we pip install using requirements.txt, like normal, within that venv.

Someone, please tell me what's wrong with this. To me, this seems much less complicated that some uv-centric .toml config file, plus some uv-centric commands for more kinds of actions.