-
Notifications
You must be signed in to change notification settings - Fork 133
VSCode reporting unresolved import on local package #669
Comments
We released a new version of the language server to the beta download channel (0.2.16). You can set this in your VS Code
I'd appreciate it if you could retest with your setup. Additionally, the Python output panel should show the list of search paths the language server is using; if your issue persists it'd be good to see it. With conda, we may need to have the extension "activate" it before launching so that the right variables are set. |
I've downloaded the beta build but it's still reporting an unresolved import. This is the Python server's output to the output panel:
Not the |
I don't believe we support egg files yet. #196 |
Since this is specifically #196 rather than the import resolution issue, changing release. |
Folding into #196 |
I'm using VSCode with the python language plugin and using a conda environment. The project is set up to use the conda environment's interpreter. I installed a local package into that conda environment recently, using
python setup.py install
. This package is now getting reported as an unresolved import in VSCode.Howevert, the package imports correctly inside VSCode from VSCode's terminal, as well as by running the file (right click -> run file in terminal). See screenshot:
This SO question appears to be describing a very similar problem, so I'm not the only one seeing this issue.
The text was updated successfully, but these errors were encountered: