Fix VS Code "No Python interpreter is selected" Error

TL;DR

Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P), run Python: Select Interpreter, and pick your Python version. If your virtualenv isn't listed, paste the path manually.

What causes this error

The Python extension needs to know which binary to use — for IntelliSense, linting, the debugger, and the integrated terminal. Without that, you get the banner:

No Python interpreter is selected. Please select a Python interpreter to enable features such as IntelliSense.

Common triggers:

• New workspace — no interpreter was ever selected
• You deleted or recreated a virtualenv and the stored path is now stale
• VS Code can't auto-detect your .venv or conda environment
• Python extension was just installed, hasn't been configured yet
• Windows install without "Add Python to PATH" checked

Fix 1: Select interpreter via Command Palette (start here)

• Hit Ctrl+Shift+P (Windows/Linux) or Cmd+Shift+P (macOS)
• Type Python: Select Interpreter and press Enter
• Pick the version you want from the dropdown

Done? Glance at the bottom status bar. It should now read something like Python 3.11.4 instead of a warning icon. That's your confirmation it worked.

Fix 2: Interpreter not listed — enter path manually

Virtualenvs created outside the workspace folder often don't show up. At the top of the interpreter list, choose Enter interpreter path... and browse to your Python binary.

Typical paths to look for:

# Linux/macOS — virtualenv
.venv/bin/python

# Windows — virtualenv
.venv\Scripts\python.exe

# conda environment
~/miniconda3/envs/myenv/bin/python

# System Python (Linux)
/usr/bin/python3

# System Python (macOS with Homebrew)
/opt/homebrew/bin/python3

Not sure where Python lives? Run this in a terminal:

# Linux/macOS
which python3

# Windows
where python

# Inside an active virtualenv
python -c "import sys; print(sys.executable)"

Fix 3: Create a workspace-local virtualenv

VS Code auto-detects .venv or venv folders sitting directly in the workspace root. Put yours elsewhere and detection breaks. Easiest fix — create one in place:

# Create .venv in your project directory
python3 -m venv .venv

# Activate (Linux/macOS)
source .venv/bin/activate

# Activate (Windows)
.venv\Scripts\activate

Reload the window (Ctrl+Shift+P → Developer: Reload Window). VS Code should detect the new .venv and prompt you to select it automatically.

Fix 4: Pin the interpreter in workspace settings

Working in a team? Lock the interpreter path so everyone gets the same environment on first open — no manual selection required. Add this to .vscode/settings.json:

{
  "python.defaultInterpreterPath": "${workspaceFolder}/.venv/bin/python"
}

Windows path (note the double backslashes):

{
  "python.defaultInterpreterPath": "${workspaceFolder}\\.venv\\Scripts\\python.exe"
}

Commit this file. Next time someone clones the repo and opens it in VS Code, the interpreter is already set.

Fix 5: Python not on PATH (Windows)

No Python options in the dropdown at all? Python probably isn't on your system PATH.

Quick check from a terminal:

python --version
# or
python3 --version

If you see 'python' is not recognized, reinstall Python from python.org. During setup, check "Add Python to PATH" — it's unchecked by default and easy to miss.

Prefer to fix it without reinstalling? Locate Python and add it manually:

# Find where Python installed itself (Windows)
where python

# Typical location:
# C:\Users\YourName\AppData\Local\Programs\Python\Python311\

# Add that folder to PATH via:
# System Properties > Environment Variables > Path > Edit

After changing PATH, do a full VS Code restart — not just a window reload.

Fix 6: Conda environment not detected

Conda envs get missed when conda itself isn't on PATH at the time VS Code launches. Get the exact Python path for your env:

# List all conda environments
conda env list

# Get the Python binary path for a specific env
conda run -n myenv python -c "import sys; print(sys.executable)"

Paste that path using the Enter interpreter path... option from Fix 2. Or, activate the conda env in a terminal first, then launch VS Code from that same terminal session — it inherits the environment.

Verification

After any fix, run through these four checks:

• Status bar — bottom-left should show the version and env name, e.g. 3.11.4 ('.venv': venv)
• IntelliSense — open any .py file and hover an import. Type hints should appear.
• Terminal match — open the integrated terminal and confirm:

python --version
# Must match what the status bar shows

• Banner gone — the yellow "No Python interpreter" notification should have disappeared

Still broken?

• Confirm the Python extension (ms-python.python) is installed from Microsoft — not a fork. Extensions panel → search "Python" → check the publisher.
• Run Developer: Reload Window after any settings change before assuming it didn't work
• Open the Output panel (Ctrl+Shift+U), select Python from the dropdown — extension error logs live there
• On remote SSH or Dev Containers: the interpreter must be selected on the remote side, not your local machine