ByteAtlas

If VS Code runs the wrong Python version, shows missing imports, or ignores your virtual environment, the selected interpreter is usually the cause. These seven checks restore a reliable setup.

1. Select the project interpreter

Open the Command Palette and run Python: Select Interpreter. Choose the interpreter inside your project virtual environment.

2. Check the status bar

Click the Python version in the status bar to switch environments. If no interpreter appears, install the Microsoft Python extension and reload VS Code.

3. Verify the integrated terminal

python -c "import sys; print(sys.executable)"
python --version
python -m pip --version

These commands should point to the same environment. Open a new terminal after changing the interpreter.

4. Recreate the virtual environment

python -m venv .venv
.\.venv\Scripts\Activate.ps1

On macOS and Linux, use source .venv/bin/activate. Then select the new environment in VS Code.

5. Check workspace settings

Review .vscode/settings.json and remove obsolete Python path values that point to an old environment.

6. Reload the extension

Run Developer: Reload Window after changing environments. Restart the language server if imports remain underlined.

7. Test the exact file

import sys
print(sys.executable)
print(sys.version)

A Run or Debug configuration can use a different environment than the terminal. Test the exact file and action that reports the problem.

Quick checklist

• Select the project interpreter.
• Verify sys.executable.
• Open a new terminal.
• Recreate a damaged .venv.
• Review workspace settings.
• Reload the Python extension.

Conclusion

Select the project interpreter, verify it from the running file, and reload the extension after environment changes. These checks solve most VS Code Python interpreter problems.