Unresolved import python visual studio как исправить

Обновлено: 06.01.2025

When pylinting a file in a big project, it appears as though libraries installed in a venv are not being discovered and thus I'm getting unresolved import issues.

Version: Visual Studio Code Version 1.33.0
Python 2.7.14 (which is what I have to use in my venv)

Sadly, I can't post a screen shot of the issues due to proprietary restrictions.
However, I am able to tab over to the Terminal window, which is pointed to my venv and open python and import each of the libraries that the Problems view indicates are problems from the linting operation without issues.

These aren't pylint errors either they are "Python(unresolved-import)" issues. Neither pytlint, pep8, or flake8 report issues with those imports.

I'll see if I can reproduce in more a basic way without proprietary libraries in the venv so that it can be fixed and add here with the details.

The text was updated successfully, but these errors were encountered:

dmayo77 commented Apr 10, 2019

Sorry about the formatting, but hopefully you get the gist.

sci-tab commented Apr 15, 2019

charce36 commented Apr 23, 2019

I have the same problem, any solution ?

jakebailey commented Apr 23, 2019

zgoda-mobica commented Apr 24, 2019

I have the same symptoms in test modules. Package is installed in current conda environment with pip install -e ., symbols are perfectly importable using basic REPL yet I still get unresolved import reported and none of IS functions work.

Package is installed properly, code runs fine. Normal code that does relative imports from source tree works fine too.

charce36 commented Apr 24, 2019

I resolved installing Ubuntu 18.04

I also have a similar problem, if I try to import any other python file it always says "unresolved" even though when I run it it works just fine.
Can someone just tell me how to disable this annoying green highlighting all over my code?

But disabling the messages won't solve the problem of the language server not finding dependencies, so the analysis will not be any better. Your issue doesn't sound the same as this issue, if it's affecting every import (and not just editable installed ones), so if you have a test project and can make a new issue, that'd be appreciated.

Edit: Sorry I've just realised you said to make a new issue, if this is not a simple fix then I will do that, and delete this comment.

Thank you for your reply Jake.
Its hard to explain the exact issue and I don't know all the correct terminology, i'm afraid I was also a bit frustrated when I posted my original comment so apologies for that.
I'm a PhD computer science student but my masters was in mechanical engineering so I sometimes make simple mistakes with this kind of stuff which may be the issue here.

Say I have files setup like this: (I've obviously omitted folders and files you don't need to see)

If I try to import Parser.py into Simulate.py as such:
import Parser
I get the unresolved import problem but the code runs just fine (as we would expect).

However if I instead put this:
import Work.Hospitality_Domain.Version_7.Parser
I do not get the unresolved import but the code does not run, (which is also what I would expect).

I get the unresolved import problem but the code runs just fine (as we would expect).

However if I instead put this:
import Work.Hospitality_Domain.Version_7.Parser
I do not get the unresolved import but the code does not run, (which is also what I would expect).

Any ideas?

I have the very same problem. There is always either en error on the IntelliSense part or while running the code.

OllieKampo commented May 18, 2019

chudytom commented May 18, 2019

Greate idea. Just please fix the link because when I click on it, it doesn't redirect me properly. I had to copy it manually.

sabretus commented May 23, 2019

I have the same problem, V1.34.0, python3.7.2, MacOS 10.14.5

mikemac8888 commented May 30, 2019

I try this extension every 6 months but bugs like this are pervasive. I have disabled all 6 available linters and these kinds of squiggly line errors which aren't really errors continue to arise. I would love a way to completely disable all visual notes in vscode from the python extension. Sadly, another six months disabling the python extension entirely.

If you don't want anything from the LS, you can disable any of the ones listed in our README, though note that "unresolved import" is special in that it means that the LS wasn't able to find an import, so the analysis quality will suffer (hence why we show it).

egabrum commented May 30, 2019

Great news! I appreciate the work you guys do, but this import issue is a deal breaker for quite a few of us, I believe.

Still happening to me on v1.35.1 / Python 3.7 / Linux

> reload window fixes it. Confirmed
(first time it was after killing a python process that was taking 100% CPU, but it seems unrelated)

jakebailey commented May 31, 2019

The 100% usage from the python process is likely unrelated; if it happens again I'd appreciate it if you could use ps or top to find the arguments given to that script and open a new issue for us to look at (so we can figure out which module is hanging when being inspected).

Luis-Palacios commented Jun 4, 2019

Is there any news on this? I'm having the same issue 😞

jakebailey commented Jun 7, 2019

I'm going through this and related issues, and for the most part you can fix things by setting extraPaths to tell us more directories to use as import roots, for example:

If you have more folders, you can list them all, and things should work.

However, this doesn't seem to work when a package gets installed as editable. I believe this has something to do with how the interpreter's own default search paths get modified and how we merge all of this configuration together. I'm currently just going through all of the test projects everyone has provided to get a good view on the unresolved imports first before trying to nail that one.

jakebailey commented Jun 7, 2019

@jakebailey Thanks for the update on the fix! :D

Is there an estimate for when this might make it to the default/stable channel? Do I need to be on an Insiders build to use the daily download channel?

jakebailey commented Jun 15, 2019

Probably within a couple days. There are some changes in 0.3.0+ that we're trying to ensure aren't causing other issues.

You do not need the insiders build to run the daily channel, just place the config in your settings and reload.

chudytom commented Jun 15, 2019

@pradyunsg try the daily channel with the fix for editable installs. I've been using it for about a week and everything works nice and smooth.
Of course, don't forget to add your library to extraPaths.

mattlefevre commented Jun 18, 2019

I did; I even tried adding each sub-folder to it (in a few different ways, because I was getting desperate and was willing to try anything). Here's all the stuff I added to extraPaths:

Is that formatted correctly? I know I don't need both "./core/posts and "./posts" , but I was just trying anything to see if it helped.

jakebailey commented Jun 18, 2019

Of those, I think only ./core should be required. Definitely not the last two, but unless you're relying on absolute imports of both posts.something and something , you should only have the one. Anything past that seems very strange.

egabrum commented Jun 18, 2019

I was wondering, regarding the editable installs, if python can find those modules, why can't the language server and I need to add them to the extra paths?

I can live with that, but it can get annoying if, as me, you work with a lot of editable installs and switch back and forth between editable and packaged.

mattlefevre commented Jun 18, 2019

That's what I thought. I've tried both of these configurations (separately) with no luck:

Editable installs use pth files, which are pretty powerful (can execute any python code at startup before any user code ever runs, but usually just contain paths) and are hard to deal with from an analysis point of view. All we can do right now is ask the interpreter "what are your paths", but the interpreter tells us this editable-installed code is a site package (because that's how pth files work), hence a configuration to tell us "no, actually this is my code".

I'd like to try and remove the extraPaths requirement, but to do that I'm going to have to research a way to distinguish what pth files are just modifying paths for the user code, which ones are doing things for libraries (matplotlib ships one which does some funky stuff), and so on, with potentially more issues. Just assuming that anything that is within the workspace is user code will not work; we can't just assume any path that lives in the workspace is user code (people put venvs in the same dir as their code).

@mattlefevre I'd appreciate it if you could enable trace logging and upload a copy of your logs. If your code is somewhere to test, that would be extremely helpful. I mainly want to see the search paths reported.

I want to use linting to make my life a bit easier in Visual Studio Code. However, for every import I have states "unresolved import". Even on default Django imports (i.e. from django.db import models).

I presume it is because it is not seeing the virtual environment Python files.

Everything works just fine, but it's starting to get annoying.

The interpreter choices I have are all system versions of Python. It does not seem to see my virtual environment Python at all (it is not in the same directory as my workspace, so that part makes sense).

If I set up the python.PythonPath in the settings.json file, it just ignores it and does not list my virtual environment path as an option. I also tried setting it up in my global Python settings, but it also does not show up.

Is there a quick fix to get it working?

29.1k 21 21 gold badges 97 97 silver badges 124 124 bronze badges 2,582 3 3 gold badges 14 14 silver badges 22 22 bronze badges pip install pylint-django , then in vs code settings add this: "python.linting.pylintArgs": [ "--load-plugins=pylint_django", ], @VaibhavVishal unfortunately, i still get the same results (added it to my settings.json file) Its actually a VScode problem that detects import package very late , after restarting it is fixed automatically. @VaibhavVishal this is the only solution that worked for me in the entire thread. Thanks. My pythonPath was already set correctly to the venv python. If this helps anyone, I actually had to install pylint in my venv: python -m pip install pylint , and then update my pylintPath in VS Code to the venv pylint.

41 Answers 41

The accepted answer won't fix the error when importing own modules.

Use the following setting in your workspace settings .vscode/settings.json :

3,817 1 1 gold badge 14 14 silver badges 24 24 bronze badges I have a mixed workspace, all python code is in a sub folder. Adding a .vscode in the sub folder will not work, this is the only working solution. This worked for me! The reference link explains perfectly. TL;DR; For user created local scripts in subdirectories, the above setting helps the python interpreter to recognize the subdirectory as its own workspace. Subsequently, recognizing scripts in the workspace and resolving imports when whole modules or individual methods are imported.

In your workspace settings, you can set your Python path like this:

33k 30 30 gold badges 106 106 silver badges 167 167 bronze badges 42.4k 7 7 gold badges 59 59 silver badges 85 85 bronze badges This sort of works. For the Python specific imports it resolves those now but not my own models (i.e. "from users.models import User" still says it cannot resolve it). Thoughts on that? Not sure. Please try reloading the window of the vs code ( from shell, code <project_directory> -r ) or just restart the vscode. I am not sure, sometimes it may occur if the workspace directory is not set properly. Please make sure manage.py is in root of workspace . Also please make sure the pylint is configured properly you genius! It was because my workspace was not starting at the root level of the project. Once i adjusted that it started work. Thanks so much! Thanks so much! Helped me get past an ages-old problem!

Alternative way: use the command interface!

Cmd / Ctrl + Shift + P → Python: Select Interpreter → choose the one with the packages you look for:

29.1k 21 21 gold badges 97 97 silver badges 124 124 bronze badges 10.6k 4 4 gold badges 51 51 silver badges 91 91 bronze badges in my case this did not work but hopefully it helps others with this issue. This worked for me. Incase anyone was still wondering in 2019. this worked for me. Because I have a directory structure where each python project I have a new venv , with this i point it to that specific Python in the venv directory for that project

This issue has already been opened on GitHub:

There are two very useful answers, by MagnuesBrzenk and SpenHouet.

The best solution for now is to create a .env file in your project root folder. Then add a PYTHONPATH to it like this:

And in your settings.json add:

29.1k 21 21 gold badges 97 97 silver badges 124 124 bronze badges 1,653 1 1 gold badge 12 12 silver badges 19 19 bronze badges Thanks @TomaszChudzik - Setting: "python.autoComplete.extraPaths": ["./src"] worked like a charm! Project root folder in vscode means where the workspace.code-workspace is and all the repos as subdirs? Module path is the path to site-packages ?

When I do > reload window that fixes it.

29.1k 21 21 gold badges 97 97 silver badges 124 124 bronze badges 1,653 4 4 gold badges 20 20 silver badges 44 44 bronze badges It just hides the warning if I click on the file, again it shows up!

If you have this code in your settings.json file, delete it:

29.1k 21 21 gold badges 97 97 silver badges 124 124 bronze badges @Tiw especially since an other answer suggest the very opposite.

None of the solutions worked except this one. Replacing "Pylance" or "Microsoft" in the settings.json solved mine.

Agreed. I also tried all the options provided but this worked!

If you are more visual like myself, you can use the Visual Studio Code configurations in menu File → Preferences → Settings ( Ctrl + , ). Go to Extensions → Python.

In the section Analysis: Disabled, add the suppression of the following message: unresolved-import :

29.1k 21 21 gold badges 97 97 silver badges 124 124 bronze badges The unresolved-import for relative imports is clearly incorrect, this gets rid of it. This only fixes the warning, not the knock on issues. If I use the python path method then the import warning disappears, and also "drill in" ("goto definition") and "parameter hints" work.

I was able to resolved this by enabling jedi in .vscode\settings.json

454 1 1 gold badge 6 6 silver badges 9 9 bronze badges Getting unknown configuration python 3.8 on v2020.8.10 of the VSC python extension

You need to select the interpreter associated with the virtual environment.

Click here (at the bottom status bar):

And just select the virtual environment you are working with. Done.

Sometimes, even with the interpreter selected, it won't work. Just repeat the process again and it should solve it.

29.1k 21 21 gold badges 97 97 silver badges 124 124 bronze badges

9,055 13 13 gold badges 66 66 silver badges 129 129 bronze badges This was exactly my problem (on mac) and selecting the proper interpreter solved it. Thanks! This was my problem. Julia apparently installed its own Python interpreter to

I wonder how many solutions this problem have (or have not), I tried most of the above, nothing worked, the only solution that worked is to set the python language server to Jedi, instead of Microsoft in the settings.json file:

None of the previous answers worked for me. Adding both of the lines below to my settings.json file did, however.

The first line really just hides the linting error. Certainly not a permanent solution, but de-clutters the screen.

Maybe someone who understands Python more than me can explain that one more.

29.1k 21 21 gold badges 97 97 silver badges 124 124 bronze badges Glad people are finding this useful, however is there anyone that can explain that second key-value pair?

My solution

This solution is only for the current project.

In the project root, create folder .vscode

Then create the file .vscode/settings.json

In the file setting.json , add the line (this is for Python 3)

This is the example for Python 2

If you don't know where your Python installation is located, just run the command which python or which python3 on the terminal. It will print the Python location.

This example works for dockerized Python - Django.

29.1k 21 21 gold badges 97 97 silver badges 124 124 bronze badges 2,675 1 1 gold badge 20 20 silver badges 28 28 bronze badges

The solution from Shinebayar G worked, but this other one is a little bit more elegant:

What I did to resolve this issue:

Go into the workspace folder (here workspaceRootFolder) and create a .env file
In this empty .env file, add the line PYTHONPATH=codeFolder (replace codeFolder with your folder name)
Add "python.envFile": "$/.env" to the settings.json
Restart Visual Studio Code

29.1k 21 21 gold badges 97 97 silver badges 124 124 bronze badges

To me the problem was related with the project that I was working on. It took me a while to figure it out, so I hope this helps:

This didn't trigger the intellisense in Visual Studio Code, but it did execute OK.

On the other hand, adding "root" on the import path, did make the intellisense work, but raised ModuleNotFoundError when executing:

The solution was to remove the _init_.py file inside the "folder" directory, leaving only the _init_.py located at /root .

2,788 3 3 gold badges 13 13 silver badges 26 26 bronze badges

Okay, so 2 years down the line I have ran into this annoying problem. All I can seen here are some really complicated workarounds. Here are easy to follow steps for anyone else who might just run into this later on:

at the bottom of VS Code where you see the Python version listed, just click there
Select Interpreter windows is going to appear
click on the first option that says "Select Interpreter Path" and navigate to the folder path which has your Virtual Environment

That's all you need to do and avoid tempering with those settings in VS Code which might get very complicated of not handled with caution.

Thanks Surveyor Jr. This actually did not work for me back in the day. So maybe there have been improvements. Thanks for adding this workaround to the thread!

This works for me:

Open the command palette ( Ctrl + Shift + P ) and choose "Python: Select Interpreter".

Doing this, you set the Python interpreter in Visual Studio Code.

29.1k 21 21 gold badges 97 97 silver badges 124 124 bronze badges

in my case. my python 2 interpreter works fine. just my python 3 not able to cooperate very well

I was facing the same problem while importing the project-related(non standard) modules. Detailed explanation of the problem

What we want:

Here "import a" and "import y" fails with following error:

What worked for me:

Appending the top directory which contains the modules to be imported.

In above example add the follwoing "Code to append" in ".vscode/settings.json"

Filename:

Code to append:

389 1 1 gold badge 5 5 silver badges 10 10 bronze badges This is what ended up working for me. I had my project with code in a package_name folder nested in an outer package_name folder. Adding just package_name to "extraPaths" (not the absolute path) did the trick. Worked for me but I had to put the directory name in quotations.

None of the answers here solved this error for me. Code would run, but I could not jump directly to function definitions. It was only for certain local packages. For one thing, python.jediEnabled is no longer a valid option. I did two things, but I am not sure the first was necessary:

Download Pylance extension, change python.languageServer to "Pylance"
Add "python.analysis.extraPaths": [ "path_to/src_file" ]

Apparently the root and src will be checked for local packages, but others must be added here.

Installing the Pylance extension immediately fixed it for me

That happens because Visual Studio Code considers your current folder as the main folder, instead of considering the actual main folder.

The quick way to fix is it provide the interpreter path to the main folder.

Press Command + Shift + P (or Ctrl + Shift + P on most other systems).

Type Python interpreter

Select the path where you installed Python in from the options available.

29.1k 21 21 gold badges 97 97 silver badges 124 124 bronze badges

Changing Python:Language Server to 'Jedi' worked for me. It was 'Windows' initially.

For me, it worked, if I setup the paths for python, pylint and autopep8 to the local environment paths.

For your workspace add/change this:

Save and restart VS Code with workspace. Done!

2,183 5 5 gold badges 10 10 silver badges 25 25 bronze badges This worked for me as well, more specifically setting the "python.linting.pylintPath" is what fixed the issue. I never had this issue until I upgraded to Python 3.9. My guess is there is a default pylint path they are using.

I am using the following setup: (in Apr 2021)

macos big sur
vscode
Anaconda 3 (for environment)

And I faced this error during starting of the Django. So, I follow these steps and this error is resolved.

Steps are given in these screenshots:

Open settings (workspace)

Follow this screenshot to open Python Path

Now, click Edit in settings.json

Make path like given in this screenshot /opt/anaconda3/bin/python

5. Now, save this settings.json file. 6. Restart the vscode

Also, intellisense might not work for some time hold on wait for some time and then restart again then vscode reads file for new path.

3,505 32 32 gold badges 27 27 silver badges 34 34 bronze badges

I have a different solution: my Visual Studio Code instance had picked up the virtualenv stored in .venv , but it was using the wrong Python binary. It was using .venv/bin/python3.7 ; using the switcher in the blue status bar.

I changed it to use .venv/bin/python and all of my imports were resolved correctly.

I don't know what Visual Studio Code is doing behind the scenes when I do this, nor do I understand why this was causing my problem, but for me this was a slightly simpler solution than editing my workspace settings.

29.1k 21 21 gold badges 97 97 silver badges 124 124 bronze badges 2,740 1 1 gold badge 31 31 silver badges 26 26 bronze badges

In case of a Pylint error, install the following

Then create a file, .pylintrc, in the root folder and write the following

29.1k 21 21 gold badges 97 97 silver badges 124 124 bronze badges

I have faced this problem in three ways. Although for each of them a solution is available in the answers to this question, I just thought to put it all together.

First I got an "Unresolved Import" while importing some modules and I noticed that my installations were happening in global pip instead of the virtual environment.

This issue was because of the Python interpreter. You need to select the interpreter in Visual Studio Code using Shift + Ctrl + P and then type Select Python Interpreter . Select your venv interpreter here.

The second issue was: The above change did not resolve my issue completely. This time it was because of file settings.json. If you don't have the settings.json file in your project directory, create one and add the following line in that:

This will basically tell Visual Studio Code to use the Python interpreter that is in your venv.

The third issue was while importing a custom Python module or file in another program. For this you need to understand the folder structure. As Python in venv is inside bin, you'll need to specify the folder of your module (most of the time the application folder). In my case it was app ,

My code references imports from a virtual environment as follows:

In my settings.json I have my pythonPath setup to use that virtualenv:

The virtualenv is setup correctly, and my code runs from the command line. However, within vscode I get "unresolved import" warnings for any imports from the virtualenv.

Expected Behavior

No 'unresolved import' warnings since the libraries exist in the virtualenv and the code runs fine on the command line.

Actual behaviour

Tonnes of 'unresolved import' warnings

Steps to reproduce:

Write code that references imports from a virtualenv virtual environment as follows:

In your settings.json set your pythonPath to use that virtualenv:

Thats it. This very setup works on mac, and does not work on linux.

The text was updated successfully, but these errors were encountered:

karrtikr commented May 2, 2019

@AlexLemna Please inform if you are using Language server or jedi, i.e check the value of setting python.jediEnabled in settings.json.

roubles commented May 3, 2019

python.jediEnabled is not present in the settings.json. So I believe it defaults to true, which is, jedi as the IntelliSense engine.

AlexLemna commented May 3, 2019

I'm really inexperienced and it's possible I've set something up wrong, but I'm getting similar errors. @karrtikr python.jediEnabled is not present in my settings.json file. I've tried to provide details below - let me know if I need to add more.

VSCode Version: 1.33.1 (user setup)
Extension version (available under the Extensions sidebar): 2019.4.12954
OS and version: Windows_NT x64 10.0.17763
Python version (& distribution if applicable, e.g. Anaconda): 3.7.3 64-bit
Type of virtual environment used (N/A | venv | virtualenv | conda | . ): venv

My files are in a directory like this:

where my main file rosevomit.py imports LogicController.py and LogicController.py imports RandomName.py and RepeatFunction.py . Both rosevomit and LogicController run fine as __main__ , but Visual Studio Code gives me warnings about importing RandomName and RepeatFunction . Here's a screenshot:

For what it's worth, I get similar (but slightly different?) errors in regular Visual Studio.

Either way, the code runs fine! It's just weird.

No worries, i'll help you do it. @roubles @AlexaLemma Can both of you please provide the following logs mentioned in the template:

Output for Python in the Output panel ( View → Output , change the drop-down the upper-right of the Output panel to Python )

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help ; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging )

karrtikr commented May 3, 2019

@AlexLemna As for your issue,

Please check this comment and this solution.

Basically python doesn't know where to look for modules by default, when you import. You have to specify the folder, in your case you need to create an .env file with content PYTHONPATH = ./Logic , to tell python to look for modules in that folder.

AlexLemna commented May 3, 2019

@karrtikr Thanks, that fixed it! I had tried the suggestions in those comments earlier, but I made the mistake of literally copy-pasting from those suggestions instead of adjusting it for my project's actual directory structure.

Basically, I had PYTHONPATH = ./core in my .env file instead of PYTHONPATH = ./core/Logic . Like you said, adding the Logic folder to the path fixed it.

Just out of curiosity - will I need to add a second PYTHONPATH statement if I add another folder with modules to my core\ folder? Or would I just shorten PYTHONPATH back to PYTHONPATH = ./core and add an __init__.py file to core\ ?

(Also - do you still need my logs now that my issue is resolved? Sorry for not including them - I'll check the template next time.)

Just out of curiosity - will I need to add a second PYTHONPATH statement if I add another folder with modules to my core\ folder? Or would I just shorten PYTHONPATH back to PYTHONPATH = ./core and add an init.py file to core?

You can either shorten PYTHONPATH and make core folder a module like you said. (Although remember to change imports to import Logic.RandomName for it to work)

You can also concatenate the same PYTHONPATH env variable to contain more module directories. See this.
In your case, PYTHONPATH=./mymodule:$ should work.

Although remember, the way of concatenating environment variables is platform dependent. See this.

karrtikr commented May 4, 2019

@roubles Please confirm if you have PYTHONPATH env specified to search for commonpy . Also, please send the logs.

Ok, so here is what I have. Under .vscode/settings.json

Let me know if any of this is not needed or superfluous.

In my project root folder I have .env

Here are the logs from Output panel:

For now, I am going back to PyCharm. This usecase works out of the box in PyCharm, and it should work of the box in VSCode as well.

Can you please also provide details for commonpy module here?
from commonpy.utils.foo import bar
Where is it located? And if PYTHONPATH is appended with that location.

potens1 commented May 19, 2019

Hi, I don't want to hijack the thread, but I've the same problem, and I don't get (at all) the comments about the PYTHONPATH, in my case I use pipenv, but should be the same as author virtualenv, the 3rd party libraries in the environment are detected, so the PYTHONPATH should be ok and my own package is installed in the env (pip(env)-e .). I can open a new bug but it sounds to me that the same (2months long, now) bug. LanguageServer or jedi have the same problem (tried both)

karrtikr commented May 20, 2019

the 3rd party libraries in the environment are detected, so the PYTHONPATH should be ok

You have to explicitly set PYTHONPATH in .env for any operation in VSCODE that depends on Python resolving modules.
So i have to ask you, do you have an .env file with PYTHONPATH specified to the location of 3rd party libraries you have to use? If not, i can help you set one up for your purpose.

In that case, I would like if you could please open up on a new issue specifying your details separately.

potens1 commented May 21, 2019

Hi, I have a very simple setup where I have a bunch of Python files in the same directory, but importing one gives the same error reported here. Works fine when I run the program. It seems strange that files in the same folder cannot be imported. PyCharm by the way has no problem with it.

Update: I had to add .env file in the project folder and define PYTHONPATH
I don't understand why this is necessary when I opened a folder containing a bunch of source files. Kind of defeats the idea of opening a folder and starting to work. The fact that you need to do this isn't mentioned in getting started either.

karrtikr commented May 21, 2019

Current scenario is that we have to explicitly set PYTHONPATH in .env for any operation in VSCODE that depends on Python resolving modules, for the reasons I mentioned earlier.

dibyendumajumdar commented May 21, 2019

@karrtikr Sure but I shouldn't need to get this info from an issue - strange that all the videos and articles about getting started with Python don't mention this upfront. Maybe because everyone demos editing a single file.

karrtikr commented May 22, 2019

Yes, i understand. Ideally you should not need to get this info from an issue.
The intent of the issue is to address this problem that it should be in Getting started.

I have been unable to get .venv import resolution with a variety of setups, mostly trying with 2019.5.18678 .
Most of my attempts have been in a multi-root context, and I am using poetry . I am unsure of how to tell if they are failing due to misconfiguration or bugs. Here a paraphrase of my latest failed attempt, modeled on the above:

I know that before yesterday I had a setup where each folder simply had a .vscode/settings.json pointing to their interpreter with a relative path, and that worked for following everything but relative imports. I tried to fix relative imports, and now the old setup doesn't work either, which is maybe the main reason I'm convinced it's a bug. Now following imports doesn't work for anything, although mypy still seems to know how to complain, and I don't get module not found linting(?) errors.

I've tried downgrading, using absolute paths, using a .env per folder, etc. But I really don't even know what folders in the venv should be added to the PYTHONPATH

I have python script which imports some libraries from subdirectories like this:

with this directory hierachy:

But VSCODE shows warnings like "unresolved import 'lib.fclib.misc' Python(unresolved-import)". And the functions in the libs have so many warnings about the codes.

The text was updated successfully, but these errors were encountered:

dkavraal commented Jan 9, 2019

The thumb ups may be confusing. I am having the same issue for the last two updates.
When I > reload window that fixes.

I have he same problem. It's really annoying. @dkavraal > reload window fix it until i try to autocomplete something or try to go to the definition

jiashengguo commented Jan 14, 2019

The same error happens for me. But if manually run the command "Running lint", it shows no error.

d3r3kk commented Jan 15, 2019

@felixchr, I cannot reproduce this on the latest version of the extension with either Jedi or the Microsoft Python Language Server (0.1.75.0) using Python 3.7.

Where is the error "unresolved import 'lib.fclib.misc' Python(unresolved-import)" coming from? If you could please include more detail from the output windows perhaps I can track down where the problem is.

What version of Python is being used?
Is there a repo I can sync to and reproduce with?
Are you using the Jedi server or the Microsoft Python Language Server?

@d3r3kk So far I don't have a repo for you. I'll generate one to reproduce it. chidgey's picture provided more detail about it. It is the same issue with me.

My environment is:
Windows 10.0.16299
Python 2.7.15
VSCode: 1.30.1
Pylint: 1.9.3
Microsoft Python extension 2018.12.1
Microsoft Python Language Server (0.1.72.0)

panosangelopoulos commented Jan 15, 2019

I faced exactly the same error, using Python 3.7.2 and docker.

My environment :
MacOSX 10.14.2 (18C54)
Python 3.7.2
VSCode: 1.30.2
Microsoft Python extension: 2018.12.1

d3r3kk commented Jan 15, 2019

felixchr commented Jan 15, 2019

I updated my environment to:
VSCode: 1.30.2
Microsoft Pythong Language server 0.1.75.0
Pylint: 1.9.4
So far everything looks good. The error is not showing anymore. The code hint and definition-follow link works good.
Thank you! @d3r3kk

chidgey commented Jan 16, 2019

I'm still seeing the same issues, oddly, I have the same VSCode and Language server as felixchr, however a newer version of pylint (all details below).

I did also follow the language server steps, thanks @d3r3kk

It might be worth noting my pylint results differ from what I see in VSCode, perhaps I've got a setting astray, judge for yourselves - it seems I see more warnings in VSCode.

I did get rid of all but the error by enabling Jedi at one point, then switched back.

PyLint
pylint 2.2.2

Python Language Server
Microsoft Python Language Server version 0.1.75.0
*This is also configured to Auto Update under settings.

System info:
Version: 1.30.2 (user setup)
Commit: 61122f88f0bf01e2ac16bdb9e1bc4571755f5bd8
Date: 2019-01-07T22:54:13.295Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
OS: Windows_NT x64 10.0.17134

The above solutions did not fix it for me.

VSCode: 1.30.2
Microsoft Python Language server 0.1.75.0

I'm using flake8 3.6.0 instead of PyLint, but I did try PyLint after reading this issue and it still happened. This only started happening in the last few weeks, with no settings changed on my end during that time.

d3r3kk commented Jan 18, 2019

@chidgey I see your problem as well, and I think I've created a minimum set of files to repro your case.

Читайте также: