vscode python modulenotfounderror

Why do I get a "ModuleNotFoundError" in VS Code despite the fact that I already installed the module?

stackoverflow.com › questions › 56658553 › why-do-i-get-a-modulenotfounderror-in-vs-code-despite-the-fact-that-i-already

After installing a new module via pip, if VS Code doesn't recognize it, then reloading VS Code may work.

Make sure the module is installed inside the virtual environment by creating and activating a virtualenv:

python3 -m venv env
source env/bin/activate

Use the correct way of installing a module with pip (Brett Cannon's article):

python3 -m pip install module_name

Replace the string "module_name" with your desired module name.

Reload VS Code by pressing Ctrl+Shift+P, and selecting Reload window.

Now it will know the new module and auto completion works.

Consider especially in new distribution like Debian 12 (Bookworm) with newer Python 3, always use a virtual environment to manage Python packages.

This is based on PEP 668, Marking Python base environments as “externally managed”.

For any new project, always create a new environment with:

python3 -m venv env

And activate it by running source env/bin/activate, and then install packages on it by pip.

Check if module_name is installed in current active virtualenv:

pip freeze

To deactivate the current active virtual environment, i.e., env run,

deactivate

Also it is worth mentioning to use the Python venv module, we must install it before.

For a Debian-based machine, here is the install command:

sudo apt install python3-venv

And same things for pip module for install a new python package.

For a Debian-based machine, here is the install command:

sudo apt install python3-pip

Answer from EsmaeelE on Stack Overflow

Stack Overflow

stackoverflow.com › questions › 56658553 › why-do-i-get-a-modulenotfounderror-in-vs-code-despite-the-fact-that-i-already

python - Why do I get a "ModuleNotFoundError" in VS Code despite the fact that I already installed the module? - Stack Overflow

Top answer

1 of 16

After installing a new module via pip, if VS Code doesn't recognize it, then reloading VS Code may work.

Make sure the module is installed inside the virtual environment by creating and activating a virtualenv:

python3 -m venv env
source env/bin/activate

Use the correct way of installing a module with pip (Brett Cannon's article):

python3 -m pip install module_name

Replace the string "module_name" with your desired module name.

Reload VS Code by pressing Ctrl+Shift+P, and selecting Reload window.

Now it will know the new module and auto completion works.

Consider especially in new distribution like Debian 12 (Bookworm) with newer Python 3, always use a virtual environment to manage Python packages.

This is based on PEP 668, Marking Python base environments as “externally managed”.

For any new project, always create a new environment with:

python3 -m venv env

And activate it by running source env/bin/activate, and then install packages on it by pip.

Check if module_name is installed in current active virtualenv:

pip freeze

To deactivate the current active virtual environment, i.e., env run,

deactivate

Also it is worth mentioning to use the Python venv module, we must install it before.

For a Debian-based machine, here is the install command:

sudo apt install python3-venv

And same things for pip module for install a new python package.

For a Debian-based machine, here is the install command:

sudo apt install python3-pip

2 of 16

sudo pip install is most likely installing globally into a Python interpreter that is different than the one that you have selected in VS Code. Please select the Python interpreter you want to use and then install explicitly using that interpreter (if you're not using a virtual environment then use something like /path/to/python -m pip install SimpleITK, although I strongly recommend using a virtual environment and to not install packages globally).

k0nze

k0nze.dev › posts › python-relative-imports-vscode

Python Relative Imports in VSCode (Fix ModuleNotFoundError and Auto-completion) | k0nze

January 30, 2024 - There is a dirty fix to remove the ModuleNotFoundError by extending the PYTHONPATH inside of main.py. PYTHONPATH is an environment variable that holds paths to additional directories in which the Python interpreter will look into to find packages and modules.

Videos