Install `pip` by default in new environments

[ikrommyd]

I think it's more logical to automatically install pip in the newly created environments by uv venv so that the user can immediately have access to pip within the new environent. Now if you create a new environment and activate it, pip points to the system pip.

Please close if this is a duplicate issue that I wasn't able to find

[charliermarsh]

Just in case you didn't see: you can run uv venv --seed to include pip, wheel, and setuptools.

[charliermarsh]

(Whether that should be the default is a reasonable question, so I'll leave this open! But wanted to make sure you knew about that option.)

[ikrommyd]

Nah, I didn't know it. Thanks! I was just comparing uv venv with virtualenv .venv and what those install to the new environment

[charliermarsh]

Yeah, we exclude these "seed" packages by default, since in theory you don't need them if you use uv to handle package installation. But if you're using uv to create virtualenvs that you want to manipulate with pip, you do need --seed.

[zanieb]

See #1330 as well

[charliermarsh]

I'm happy with our current choice here, though I know it can take some adjustment for users.

[ikrommyd]

Yup, I should have actually closed it myself, I had just forgotten about it.

[charliermarsh]

All good, thanks for following up :)