Python ModuleNotFoundError no module named

What this error means

ModuleNotFoundError: No module named means Python is using an interpreter, package environment, certificate store, or virtual environment that does not match what the script expects.

Common causes

• Package is not installed in the active environment
• pip and python point to different interpreters
• Import name differs from package name
• Virtual environment is not activated

Copy-paste commands

Check Python version

python3 --version

Check pip target

python -m pip --version

List installed packages

python -m pip list

Create a virtual environment

python -m venv venv

Activate on macOS/Linux

source venv/bin/activate

Quick fixes

1. Check the active interpreter with python3 --version.
2. Use python -m pip so pip targets the interpreter that runs the code.
3. Run python -m pip install inside the environment used to run the script.
4. Recreate the virtual environment if the interpreter version changed.

Step-by-step troubleshooting

1. Confirm the failing traceback contains ModuleNotFoundError: No module named.
2. Run python -m pip --version and verify the path belongs to the expected environment.
3. Activate the virtual environment, then rerun the same version and pip checks.
4. Install packages with python -m pip install <package> rather than a bare pip command.
5. Retry the smallest script or import that produced the error.

Platform-specific fixes

macOS

• If system Python and Homebrew Python both exist, use python3 -m pip from the interpreter you run in production.

Linux

• On Debian/Ubuntu, install virtual environment support with sudo apt install python3-venv when ensurepip is missing.

Windows

• Use py -m pip --version and py -m venv venv when the Python launcher is installed.

Real-world fixes

• If imports fail after installation, the package was likely installed into a different interpreter.
• If SSL fails only in Python, update the CA bundle used by Python before disabling verification.
• Run python -m pip install inside the environment used to run the script.

How to prevent it

• Use a virtual environment per project.
• Record dependencies in requirements.txt, pyproject.toml, or the project lockfile.
• Use python -m pip in documentation and CI scripts.

Related errors

• ImportError cannot import name
• pip command not found
• Python SSL certificate verify failed

FAQ

What should I check first?

Start with the exact ModuleNotFoundError: No module named line and the command, request, or workflow step that produced it. In Python, the first useful clue is usually near the first failure line, not the final stack trace.

Can I ignore this error?

No. Treat it as a failed Python step. A temporary bypass may help diagnosis, but the underlying cause should be fixed before shipping or publishing changes.

Why does this work locally but fail elsewhere?

Local machines often have cached credentials, old dependencies, different runtime versions, or network settings that CI and production do not share. Reproduce from a clean shell or clean install when possible.

How do I know the fix worked?

Rerun the smallest command, request, or deployment step that produced ModuleNotFoundError: No module named. The fix is working when that step completes without the same signature and produces the expected output.