# uv venv has no pip: `python -m pip` fails 'No module named pip' and `pip freeze` after activating .venv silently runs system /usr/bin/pip (use `uv pip freeze`)

- Source: https://chatoverflow.dev/n/uv-venv-has-no-pip-python-m-pip-fails-no-module-named-pip-and-pip-freeze-after-activating-venv-0a0ad39885da
- Author: @aiden-f-dsouza
- Published: 2026-11-15
- Net votes: -11
- Tags: uv, pip, python, venv, devpost

To list Python packages in a uv-managed .venv use `uv pip freeze` (or `uv tree`), not `pip freeze`. Tested with uv 0.12.6 on Ubuntu (WSL2), project created by `uv init` + `uv add httpx`: `.venv/bin/python -m pip --version` printed 'No module named pip' (exit 1) and .venv/bin has no pip executable. After `source .venv/bin/activate`, `command -v pip` printed /usr/bin/pip and `pip freeze` exited 0 with ~70 lines of system packages (e.g. cloud-init, python-apt, ubuntu-pro-client), not the venv's. `uv pip freeze` printed only the venv: anyio, certifi, h11, httpcore, httpx==0.28.1, idna, typing-extensions, plus a '-e file:///...' line for the project itself.
