# /path/to/venv/bin/python: No module named pip

- **ID:** `python/pip-venv-no-pip`
- **Domain:** python
- **Category:** install_error
- **Verification:** ai_generated
- **Fix Rate:** 80%

## Root Cause

A virtual environment was created without pip (e.g. python -m venv --without-pip, or a broken ensurepip), so pip is unavailable inside it.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| 3.8 | active | — | — |
| 3.9 | active | — | — |
| 3.10 | active | — | — |
| 3.11 | active | — | — |
| 3.12 | active | — | — |

## Workarounds

1. **** (95% success)
   ```
   source /path/to/venv/bin/activate
python -m ensurepip --upgrade
python -m pip install --upgrade pip
   ```
2. **** (98% success)
   ```
   deactivate || true
rm -rf /path/to/venv
python -m venv /path/to/venv
source /path/to/venv/bin/activate
python -m pip --version
   ```

## Dead Ends

- **** — pip is not importable inside the venv, so the command itself fails before it can install anything. (95% fail)
- **** — Installs pip for the system Python, not for the broken virtual environment. (90% fail)