Reportmissingimports python как исправить

Pylance, by default, includes the root path of your workspace. If you want to include other subdirectories as import resolution paths, you can add them using the python.analysis.extraPaths setting for the workspace.

• In VS Code press <ctrl> + <,> to open Settings.
• Type in python.analysis.extraPaths
• Select «Add Item»
• Type in the path to your library /home/andylu/Dokumente/Allgemeines_material/Sonstiges/Programming/Python/Scripts/

Pylance, by default, includes the root path of your workspace. If you want to include other subdirectories as import resolution paths, you can add them using the python.analysis.extraPaths setting for the workspace.

• In VS Code press <ctrl> + <,> to open Settings.
• Type in python.analysis.extraPaths
• Select «Add Item»
• Type in the path to your library /home/andylu/Dokumente/Allgemeines_material/Sonstiges/Programming/Python/Scripts/

Two methods below:

1. In VS code you can edit the setting.json file. If you add "python.analysis.useImportHeuristic": true the linting error will be removed.

2. The alternative is to add # type: ignore at the end of the import code.

Here is the github link that i got the above resolution from: https://github.com/microsoft/pylance-release/issues/68

It worked for me: python 3.9, VScode, windows10

By default python selects the global interpreter as the interpreter for any python project you have. So the module/package resolution is in the global context. For any linter you are using to pick up your installed modules you have to ensure you select the correct interpreter

For instance, if you have ever worked with pycharm it does ask you to select the interpreter and create virtual environment with the selected interpreter. For the same, if you start a project in visual studio code It takes the global interpreter as the default interpreter even if you create a virtual environment See this on the bottom left section for the selected interpreter

So how do you ensure Pylance/Pylint/ reads modules installed in the virtual environment created? You need to check for the selected interpreter at the bottom left and if not activated on the virtual environment click on the selected interpreter and vs-code will prompt you to select a default interpreter for the project. Select your current virtual environment and visual studio pylance will read the modules in the current environment. Hope this works for anyone who’s struggling with the same

I was facing similar issue, even after having packages on my system, VS Code Pylance was not able to resolve imports.

In my case I had 2 different versions of python installed (one using anaconda distribution and other directly from python.org)

Fix: Select right python interpreter in VS code. Pylance will stop complaining

Another option is to add an .env file at the root of the vscode project. For example:

.env

PYTHONPATH=src/mydir

You either use a relative path like above, or the full path. The benefit of .env is that it will fix both pylance and pylint in vscode. And it’s easier to commit and share on git than .vscode/settings.json.

Pylance is the default the language server used for python project unless you specify it otherwise. If you get (reportMissingImports) and you are sure the dependency has been successfully installed, it means it’s installed somewhere else than Pylance expected. This usually happens if you are working with virtual environements.

Pylance by default selects the system python interpreter for any python project, in this case you need to tell Pylance where to find the virtualenv python interpreter by defining this your vscode settings. Under .vscode/settings.json add the following:

{
    "python.defaultInterpreterPath": "~/.pyenv/versions/3.10.2/envs/<my-virtual-env-name>/bin/python",
    "python.linting.ignorePatterns": [
        "**/site-packages/**/*.py"
    ],
}

Now Pylance will know exactly where to look for the installed dependency. In my case I’m using pyenv but it may be any other path depending on what virtualenv tool you use. If you have other dependencies in other custom location, you can add them by specifying "python.analysis.extraPaths":

{
    "python.defaultInterpreterPath": "~/.pyenv/versions/3.10.2/envs/<my-virtual-env-name>/bin/python",
    "python.linting.ignorePatterns": [
        "**/site-packages/**/*.py"
    ],
    "python.analysis.extraPaths": [
        "my-custom-path-1/python/scripts", 
        "my-custom-path-2/something-else"
    ],
}

If you are using Anaconda environment, a workaround is to add your personal library path to ‘python library path’ via the command conda develop path/to/your/module.

Solution

Add this to your settings.json in vscode:

   "python.analysis.extraPaths": ["ml/py"],

it can be a relative path based on the root of your project or an absolute path. You can also have several of them.

In VS studio code

1. Open your folder
2. Right Click on the workspace where all the files or folders are
3. Add folder to workspace
4. Select the directory on what you inputted in sys.path.insert("DIRECTORY")

I faced similar issue and resolved it by,

1. Opening the Command Palette (Ctrl+Shift+P).
2. Search and Select Interpreter.
3. Browse & Select the virtual environment that you are working with,
4. Navigate to the scripts folder and select the python application.

and voila all your yellow squiggly lines disappear like fart in thin air. Quote credit: Warden from SSR.

Comments Section

will it resolve if you do import General, what if you add the path to PYTHONPATH before starting VSC. Maybe PyLance only wants relative paths in "python.analysis.extraPaths"

Thanks for your hint. It made me try out additional measures (see EDIT of my initial post above). I still get the same warning message from pylance. Apart from that, an absolute path should always work as far as I’m concerned, but even if this was the issue, now there are all python— and sys-paths set within my project-venv, and still pylance doesn’t recognize it.

then consider filing an issue with PyLance not adhering to PYTONPATH, but how do the virtual environments merge the local and system installed modules, PyLance can handle these

Now, for some reason, it stopped throwing the warnings. I don’t know how it got resolved, but for now I closed the issue posted on the pylance GitHub website: github.com/microsoft/pylance-release/issues/724

Thanks for your reply. Yet, as you can see in my post, I’ve already tried that with no avail. Maybe it has an effect now. As soon as I get to try it out, I’ll let you know.

i get the same linting issue. It appears as though there is still no solution other than to add # type: ignore at the end of the import statement.

Thanks for your contribution. I’ve also followed the git-discussion and saw the "python.analysis.useImportHeuristic": true, I’ll try it out once I get to it. As for the 2nd alternative, this workaround was already mentioned in my initial post and seems to be the last resort, if nothing else works.

comment noted. I confirm that both methods work on the setup that i have, although it seems that you are using Lubuntu 20.04 whereas i tested on windows10. so would be useful to know that it is platform agnostic or otherwise.

Just checked it on Windows 10, in my settings.json the line "python.analysis.useImportHeuristic": true is greyed out. When I hover over it, it states «Unknown Configuration Setting».

@AndreasL. Same happened to me when I got the "Unknown Configuration Setting". Did you find a workaround for this?

Is there a less specific solution? I mean, if I use this solution, I have to add all the paths to all the folders where any test scripts are located.

I use virtualenv for my (Django) project and I had to reference the path for this to work: ~/.virtualenvs/<project directory>/Lib/site-packages/

This is expected as it is a hidden option. github.com/microsoft/pylance-release/issues/…

In addition to this, make sure to select and activate the correct Python environment.

This works perfectly when the «source» folder is named something else than «src».

This works, but some of us are also trying to add other sys.paths outside of the current env, and Pylance will not recognize them, even if they are setup correctly and work when we run the py files. This Example was the only thing that worked for me.

You can add those paths in the ./vscode/settings.json from where vscode reads all configurations from if the settings.json is set

why would a Multi Root Workspace solve the PyLance reportMissingImports problem, where in Explorer do you right click? Add Folder to Workspace is part of the File menu

Related Topics
python-3.x
visual-studio-code
pylance
vscode-settings
python-import

Mentions
Dhia
Felix Orinda
David Dehghan
Edward Funny Hands
Ryan
Wisbucky
Tarun Kumar
Xiaoyue Cao
Adrian Ladia
Lin Felix

References
stackoverflow.com/questions/65252074/import-path-to-own-script-could-not-be-resolved-pylance-reportmissingimports