Hi! I'm using a tool called Meltano which supports uv as an alternate virtual environment backend. In our case, I would be great if pip was still bundled with the venvs uv creates for legacy reasons, which I can see is possible with the uv venv --seed. Since we don't have direct control over how uv venv runs behind the scenes, would it be possible to expose configuration for this via an environment variable (e.g. UV_VENV_SEED=true)?

Worth noting that I was running into #6593 initially - here is part of the message I sent in their Slack:

I'm trying out uv as a venv backend, and it has been great up until running the notebook utility. Some of our notebooks contain an initial cell to pip install dependencies to the venv - with uv, this no longer works properly because pip isn't bundled with the venv, so dependencies are installed to the system Python instead and then cannot be imported later on in the context of the venv Python.