# ModuleNotFoundError: No module named 'pip' after python -m venv .venv && source .venv/bin/activate

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

## Root Cause

The venv was created without pip. This happens on Debian/Ubuntu when python3-venv is not installed, or when venv is created with --without-pip, or on some minimal Docker images.

## 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)
   ```
   rm -rf .venv && python3 -m venv .venv && source .venv/bin/activate && python -m pip --version
   ```
2. **** (90% success)
   ```
   python -m ensurepip --upgrade
   ```
3. **** (92% success)
   ```
   sudo apt update && sudo apt install python3-venv python3-pip
   ```

## Dead Ends

- **** — pip is not available to install itself; the module is missing. (95% fail)
- **** — Installs pip for the system interpreter, not inside the venv. (85% fail)