Import could not be resolved/could not be resolved from source Pylance in VS Code using Python 3.9.2 on Windows 10

Question

My Flask App server is running but I have three imports that cannot be resolved.

I have tried:

1. reinstalling the imports individually
2. reinstalling requirements.txt
3. I configured VSCode Workspace with an extra path to my project folder (there is now a .vscode file within the root of my project folder where it was not before)
4. I have updated my venv path settings in VSCode

Here is my file structure:

- > .vscode
- > client *(React front end)*
- > data
- > server *(Python/Flask back end)*
    - > app
    - > venv
    - config.py
    - README.md
    - requirements.txt *(this contains the 3 unresolved, along with several that are resolving)*
- .env
- .flaskenv
- .gitignore
- requirements.txt

Unfortunately none of these things have resolved my imports issue and my routes are still not working. Any ideas/suggestions?

Subtropics

Answer 1

1. Open the Command Palette (Ctrl+Shift+P), then select the Python: Select Interpreter. From the list, select the virtual environment in your project folder that starts with .env.

2. Run Terminal: Create New Integrated Terminal (Ctrl+Shift+` or from the Command Palette), which creates a terminal and automatically activates the virtual environment by running its activation script.

3. Install sqlalchemy and mongoengine with command pip install. Once installing them successfully, there will intellisense when you import them and no warnings shown.

Besides, the folder .vscode is to store Workspace settings as well as debugging and task configurations.

Julianajuliane

Re step 1: the list that appears when I click on 'Python: Select Interpreter' does not include one that starts with the name of my project's virtual environment. – Subtropics

"Terminal: Create New Integrated Terminal" was not an option for me but "Terminal: Create New Terminal (In Active Workspace)" was and that worked for me. – German

What if I already have the sqlalchemy and mongoengine installed? Pylance is still throwing me error, I've updated my "python.defaultInterpreterPath" appropriately to point to the virtual environment. – Ace

None of these instructions has worked for me so far. It's worth to be said I'm using the "Insiders" version of VSCode (I need it to make Copilot Chat work) – Jameejamel

Answer 2

To resolve the issue, perform the following steps:

1. Open the Command Palette by pressing Ctrl+Shift+P on your keyboard.
2. In the Command Palette, select Python: Clear Cache and Reload Window.

Nutshell

On a related note, if you import like this: from sqlalchemy import Column... It may complain about spelling. It provides a quick fix to update your .vscode/settings to make this word known. This, plus the much-appreciated suggestion above is what cleared it up for me. – Drank

Answer 3

If you are using a virtual environment, and even after trying pip installing all the necessary libraries, you have to select the python interpreter that exists in the virtual environment folder.

1. (Ctrl+Shift+P) then search for "Python: Select Interpreter"
2. Click "Enter interpreter path" followed by "Find.."
3. Navigate to your project virtual environment folder
4. Go into "Scripts" folder and then select "python.exe" as the interpreter.

These steps allow you to select the right python interpreter associated with the project's virtual environment.

Kappel

This worked for me, but for me the interpreter I selected was bin/python (symlink to /usr/bin/python3) – Carpophagous

Also worked for me, but in my case (on Linux) I'm using python installed using nix. So I first did which python to get the location of the python binary, and looked for that particular binary in the list of interpreters. That worked! – Harrietharriett

This works but I worry about the fact that vscode says "Unknown configuration setting" when I hover over this. – Trenna

script folder not showing – Lorenza

This worked, except I had to navigate to the path of which python in my venv – Claytor

For poetry poetry show -v then you will find the path just copy and paste. – Quadruplet

This worked for me, but for me the interpreter I selected the conda or venv folder where the packages were installed – Observatory

Answer 4

I specified a path to the python interpreter I'm using within the settings.json file contained in the project repo's .vscode folder.

"python.pythonPath": "path-to-interpreter.python.exe"

Thanks to the following resource! https://dev.to/climentea/how-to-solve-pylance-missing-imports-in-vscode-359b

Subtropics

Unlike the previous solutions - This worked for me, but more specifically I set python.pythonPath to the result of running which python FROM WITHIN the VSCode Integrated Terminal that is accessed via Ctrl-Shift+`. This is a different path than running it in a normal term window, as it is inside your virtual env. – Deathlike

Answer 5

I ran into this error after an upgrade of my local python version (brew -> manual install), even though the specified interpreter was already /usr/local/bin/python3.

CMD + Shift + P and re-selecting the [same] interpreter fixed the error.

In hindsight, I suspect that a restart of VSCode could have also fixed this. 🤷‍♂️

Buroker

This worked for me. Only difference is that I manually entered my interpreter's path, since I was working on an external Linux machine. I simply typed which python in the terminal and copy-pasted the file location into the interpreter's path. – Senate

Answer 6

I work on a windows machine. I use miniconda to manage my virtual environments. And when I'm coding I launch every program from the command prompt (cmd), including Vscode.

Even tough inside Vscode the Python evironment was correctly set, I was getting the very same import error that you mention. The interesting part of it was that I wasn't having any problems to run the code, it was working as usual. But when coding, I wasn't able to see the functions related to the libraries with the import error.

The solution:

Activate the correct conda env for the project before launching Vscode from the command prompt.

Why does this happen?

I BELIEVE that this happens because when you don't activate any conda env before launching Vscode, the base conda env is loaded as default. That generates the import conflict (You can chek this out by installing those packages into the environment and running everything just as you have been doing).

Ultima

Answer 7

1. Run pip --version and copy the site-packages path. (don't take the whole pip path, just the folder location)
2. Open settings on VS, and type @ext:ms-python.vscode-pylance on the settings search bar.
3. Find the Python › Analysis: Extra Paths setting.
4. Click Add Item and paste the copied value.

Fernandafernande

Answer 8

After making sure my Python environment was set correctly, I did a View->Command Palette...->Developer: Reload Window

Apparently, in my case, pylance needed the window reloaded to get proper context.

Disparity

Answer 9

Selecting the Python Interpreter and then Clearing cache with reload window worked for me.

Formula

Answer 10

Perhaps VSCode is using the incorrect Python path for this reason. A base interpreter should be used instead of the vscode interpreter, if necessary.

Wellread

Answer 11

After verifying my Python interpreter was sourced correctly in VS Code, I simply cleaned my env and reinstalled the project locally and the import errors disappeared. I personally had an odd VS Code/Pylance cache and reinstalling the dependencies and modules fixed it for me.

Ignatia

Answer 12

This might not have been relevant in your case but if you open an interactive pane in VS Code then VS Code will stick with that environment no matter what you set it to instead. So close the interactive window, switch away from and then back to the environment you want to use.

Collocation

Answer 13

For VSCode, use the following command to install dependency packages into project's virtual environment:

.venv\scripts\python -m pip install -r requirements.txt

Padegs

Answer 14

For miniconda, I had to install python-dotenv with conda install python-dot-env. I tried passing target flag to pip.

Saprolite

Answer 15

Using the windows option "connect to a network drive" I connected my computers to the place where I stored the file.

Now it works fine.

Unofficial