ModuleNotFoundError: No module named 'requests'
ImportError: cannot import name 'xyz' from 'module'

Python can’t find the module you’re trying to import. This is one of the most common Python errors, and it has several distinct causes — from missing packages to environment mismatches to naming conflicts.

Why this happens

When you write import requests, Python searches for the module in this order:

1. The current directory
2. Directories in PYTHONPATH environment variable
3. The standard library
4. Installed packages (site-packages)

If the module isn’t found in any of these locations, Python raises ModuleNotFoundError. If the module is found but the specific name you’re importing from it doesn’t exist, you get ImportError.

Fix 1: Install the missing package

The most common cause — the package simply isn’t installed.

# Install with pip
pip install requests

# If you have multiple Python versions, be explicit
pip3 install requests
python3 -m pip install requests

# For a specific version
pip install requests==2.31.0

# From a requirements file
pip install -r requirements.txt

Verify it’s installed:

pip show requests
# Shows: Name, Version, Location, etc.
# If "WARNING: Package(s) not found" — it's not installed

Fix 2: Wrong Python environment (most frustrating)

You installed the package, but Python is using a different interpreter that doesn’t have it.

# Check which Python is running
which python3
# /usr/bin/python3 ← system Python

python3 -c "import sys; print(sys.executable)"
# /usr/bin/python3

# Check where pip installs to
pip3 show requests | grep Location
# /home/user/.local/lib/python3.11/site-packages

# But your script might be using a different Python!

The fix: Always use python -m pip to ensure pip matches your Python:

# This guarantees pip installs for the same Python that runs your code
python3 -m pip install requests

# Or in a virtual environment (best practice)
python3 -m venv .venv
source .venv/bin/activate
pip install requests
python3 app.py  # Uses .venv's Python with requests installed

Fix 3: Virtual environment not activated

You created a venv and installed packages there, but you’re running the script with system Python.

# ❌ Running without activating
python3 app.py  # Uses system Python — no packages from venv

# ✅ Activate first
source .venv/bin/activate    # Linux/Mac
.\.venv\Scripts\activate     # Windows PowerShell
.venv\Scripts\activate.bat   # Windows CMD

# Now python3 and pip point to the venv
python3 app.py  # Uses venv Python with all installed packages

# ✅ Or run directly with the venv's Python
.venv/bin/python3 app.py  # No activation needed

IDE tip: In VS Code, select the interpreter (Ctrl+Shift+P → “Python: Select Interpreter”) and choose your venv. This ensures the terminal and debugger use the right Python.

Fix 4: File name conflicts with module names

If you have a file named the same as a package, Python imports your file instead of the package.

# ❌ You have a file called "requests.py" in your project
# Python imports YOUR file, not the pip package
import requests  # ImportError or unexpected behavior

# ❌ Other common conflicts:
# email.py, json.py, random.py, test.py, typing.py, collections.py

Fix: Rename your file to something that doesn’t conflict:

mv requests.py http_client.py
mv email.py email_sender.py
mv test.py test_app.py

# Also delete the cached .pyc file
rm -rf __pycache__

How to detect: If import requests works in the Python REPL but not in your project, you likely have a naming conflict.

Fix 5: Package name ≠ import name

Some packages have different names for pip install vs import. This trips up everyone.

pip install	import as
Pillow	PIL
python-dotenv	dotenv
opencv-python	cv2
scikit-learn	sklearn
beautifulsoup4	bs4
python-dateutil	dateutil
PyYAML	yaml
Pygments	pygments

# ❌ Wrong install name
pip install PIL  # Package doesn't exist!

# ✅ Correct
pip install Pillow
python3 -c "from PIL import Image"  # Works

Fix 6: Circular imports

Two modules importing each other creates a circular dependency. Python can’t resolve it.

# ❌ a.py imports from b.py, b.py imports from a.py
# a.py
from b import helper_b  # ImportError!

# b.py
from a import helper_a

Fixes:

# ✅ Option 1: Import inside the function (lazy import)
def my_function():
    from b import helper_b  # Only imported when function is called
    return helper_b()

# ✅ Option 2: Move shared code to a third module
# shared.py — no imports from a or b
def shared_helper():
    pass

# ✅ Option 3: Import the module, not the name
import b  # Import the module
b.helper_b()  # Access the name later

See Python ImportError Circular — Fix for more patterns.

Fix 7: Relative import errors

# ❌ Relative import in a script run directly
from .utils import helper  # ImportError: attempted relative import with no known parent package

# ✅ Option 1: Use absolute imports
from mypackage.utils import helper

# ✅ Option 2: Run as a module
python3 -m mypackage.main  # Instead of python3 mypackage/main.py

Relative imports only work when the file is part of a package (has __init__.py) and is imported, not run directly.

Fix 8: Missing __init__.py (Python packages)

For Python to recognize a directory as a package, it needs an __init__.py file (can be empty).

myproject/
├── main.py
├── utils/          ← directory
│   ├── __init__.py ← REQUIRED (can be empty)
│   └── helpers.py

# Without __init__.py:
from utils.helpers import my_func  # ModuleNotFoundError

# With __init__.py:
from utils.helpers import my_func  # Works

Note: In Python 3.3+, “namespace packages” work without __init__.py, but it’s still best practice to include it for clarity.

Debugging checklist

import sys

# 1. Which Python am I using?
print(sys.executable)

# 2. Where does Python look for modules?
print('\n'.join(sys.path))

# 3. Is the package installed?
import importlib
spec = importlib.util.find_spec('requests')
print(spec)  # None = not found

# 4. Where is the package?
import requests
print(requests.__file__)

FAQ

Why does pip install succeed but import still fails?

pip installed to a different Python than the one running your script. Use python3 -m pip install to ensure they match, or check which python3 vs pip3 show <package> | grep Location.

How do I fix this in Docker?

Make sure your Dockerfile installs packages for the same Python that runs the app:

RUN pip install --no-cache-dir -r requirements.txt
CMD ["python3", "app.py"]

Why does it work in Jupyter but not in my script?

Jupyter might be using a different kernel (different Python installation). Check with !which python in a Jupyter cell and compare to your terminal’s which python3.

How do I fix “ImportError: cannot import name X from Y”?

This means the module exists but doesn’t have the name you’re importing. Common causes: wrong version of the package (the function was added in a newer version), typo in the name, or you’re importing from your own file that shadows the package.

Related errors

• Python ImportError Circular — Fix
• Python ImportError Cannot Import Name — Fix
• pip Externally Managed — Fix
• pip Install Error — Fix
• Python FileNotFoundError — Fix
• Python Cheat Sheet