Import can not be resolved error in pylance jupyter notebook for importing .py file in same directory as notebook #3017

jj-github-jj · 2022-07-08T01:50:53Z

Environment data

Language Server version: 2022.7.20
OS and version: win32 x64
Python version (and distribution if applicable, e.g. Anaconda): 3.9.5 but also many versions like 3.10 have the same issue
python.analysis.indexing: null
python.analysis.typeCheckingMode: off

Code Snippet

import myfunctions as mf
#myfunctions.py in same directory as notebook

XXX

Expected behavior

hovering over mf.function() should show docstring etc

Actual behavior

no doc string since pylance reports import can not be resolved error.
Also noticed on a fresh dev machine install of vscode is actually showing the correct behavior for
one file i.e import myfunction as mf is working but in another ipynb file in the same directory opened in the same workspace at the same , import myfunction as mf does not work for pylance but

import myfunction

mf = myfunction

mf.function()
does work as expected in showing doc string for myfunction etc.

seems like workspace files are creating issues. If I open folder containing myfunction.py and the caller.ipynb after deleting any workspace files, things are working as expected. But after adding folders to workspace (a parent folder of the current folder) and saving as workspace file, pylance starts giving import can not be resolved errors.. My workaround is to delete all workspace files, open just the folder and pylance is happy

Logs

XXX

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

vvvv0208 · 2022-07-11T10:17:13Z

Me too, the same code, after updating vscode, reported such an error “Import "model_2" could not be resolved Pylance(reportMissingImports)”

debonte · 2022-07-11T21:26:26Z

@jj-github-jj, can you search for "LSP Notebooks experiment" in the Jupyter log and tell me what that line says. It's likely either:

LSP Notebooks experiment is disabled -- not in treatment group

or

LSP Notebooks experiment is enabled

If you see LSP Notebooks experiment is enabled, can you try setting "python.pylanceLspNotebooksEnabled": false in your VS Code settings, reload VS Code, and see if that fixes the behavior?

laye0619 · 2022-07-12T13:14:34Z

I have exact same issue... set the python.pylanceLspNotebooksEnabled but it didn't work....

Nufflee · 2022-07-15T03:59:26Z

Setting python.pylanceLspNotebooksEnabled to false has fixed it for me, and I did have it enabled previously according to the log.

I have exact same issue... set the python.pylanceLspNotebooksEnabled but it didn't work....

@laye0619 Did you make sure to set it to false, not true?

laye0619 · 2022-07-15T05:25:17Z

Setting python.pylanceLspNotebooksEnabled to false has fixed it for me, and I did have it enabled previously according to the log.

I have exact same issue... set the python.pylanceLspNotebooksEnabled but it didn't work....

@laye0619 Did you make sure to set it to false, not true?

I've already set the "python.pylanceLspNotebooksEnabled": false in my setting json file and reloaded... but seems that it was still not working.... searched the 'LSP Notebooks experiment' in Jupiter log and found that LSP Notebooks experiment was still enabled....

jj-github-jj · 2022-07-20T22:35:45Z

Tried setting "python.pylanceLspNotebooksEnabled": false in user\settings.json, reloaded vs code and still have cant resolve import errors.

heejaechang · 2022-08-08T21:23:31Z

This issue has been fixed in version 2022.8.12, which we've just released. You can find the changelog here: CHANGELOG.md

Yura52 · 2022-08-15T10:23:53Z

@heejaechang the issue is still there, though in a different form. This is my project structure:

- lib/
    - __init__.py
    - whatever.py
- myfolder/
    - a.ipynb 
    - a.py

import lib in myfolder/a.ipynb causes Import "lib" could not be resolved
moving myfolder/a.ipynb to the project root fixes the issue
import lib in myfolder/a.py does not cause any issues

ccrvlh · 2022-08-16T20:38:44Z

@debonte solution works for me, although I do have to correct the path when running from a sibling:
With the following folder structure

- app/
    - myfile.py
- notebooks/
    - mynotebook.ipynb

I have to put this on top of the first cell.

import sys, os
sys.path.insert(0, os.path.abspath('..'))

MrYutz · 2022-08-18T20:41:58Z

The same overall issue for me. Code runs but Pylance isn't happy. It was working last week. Currently on Pylance 2022.8.31

- modules
    - module1.py
- notebooks
    - notebook.ipynb

Xabitsuki · 2022-08-25T08:39:44Z

Same here with a local library installed in editable mode in conda environment: the package is correctly imported and documentations are displayed for all modules in the package but not whenever I import the package in a notebook.
Code runs but pylance complains.

I tried the

"python.pylanceLspNotebooksEnabled": false which has not effect.
adding "python.analysis.extraPaths": ["{workspaceFolder}/mypackage"] to workspace settings

--> did not solved it

About VS Code
Version: 1.70.2 (Universal)
Commit: e4503b30fc78200f846c62cf8091b76ff5547662
Date: 2022-08-16T05:36:37.829Z (1 wk ago)
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: 10.0.139.17-electron.0
OS: Darwin x64 21.6.0

YDX-2147483647 · 2022-08-25T13:01:54Z

@Xabitsuki Is ["{workspaceFolder}/mypackage"] a typo? I mean there should be a dollar sign (${workspaceFolder}).

bschnurr · 2022-08-25T16:40:44Z

This issue has been fixed in version 2022.8.41, which we've just released. You can find the changelog here: CHANGELOG.md

Michaelzhouisnotwhite · 2022-09-02T14:26:59Z

This issue has been fixed in version 2022.8.41, which we've just released. You can find the changelog here: CHANGELOG.md

Do I still need to diable pylanceLspNotebooksEnabled and change python.analysis.extraPaths in next version? My vscode version now is 1.71.0

torext · 2022-09-09T12:48:13Z

The issue still persists on my side with the latest versions of VSCode (1.71.0) and Pylance (2022.9.10):

- testworkspace/
    - modules/
        - class_defs.py
    - notebooks/
        - notebook.ipynb

with class_defs.py contents:

class MyClass:
    ...

antonioalegria · 2022-09-13T09:23:21Z

With the latest version of VS Code (1.71.0), Pylance 2022.9.10, the problem is still there. Only works after disabling LSP Notebooks experiment and setting the analysis path, and then restarting all the kernels, etc...

MrYutz · 2022-09-13T12:20:56Z

Same for me. The issue persists.

debonte · 2022-09-13T19:25:11Z

@MrYutz, @antonioalegria, @torext, it's likely that you are seeing #3208. We'll be shipping a fix for that in prerelease tomorrow.

debonte · 2022-09-15T04:19:08Z

@MrYutz, @antonioalegria, @torext, it's likely that you are seeing #3208. We'll be shipping a fix for that in prerelease tomorrow.

#3208 has been fixed in prerelease version 2022.9.21, which we've just released. You can find the changelog here: CHANGELOG.md

elashrry · 2022-09-15T09:51:44Z

VSCode (1.71.1) and Pylance (2022.9.21).

I tried to confirm the fix, and everything works fine when I create a new workspace. However, with the workspace I have been working on, it doesn't seems to work. I restarted VSCode, I deleted all workspace settings, but no fix. Why is this happening? The current workspace is a git repo, I don't know if this matters.

I also tried it with other workspaces that are git repos, and everything seems to work.

Update

I think I get the reason for the problem, but I don't know how to solve it.

The situation is like

root/
    work/
        test.py
        test.ipynb
        module.py
    tools/
        sub_folder/
            other_module.py
            test.py
            test.ipynb

I use conda environment and I add the tools/ foler to the python path by running command

conda develop ./tools

from the root folder.

Everything work fine in the work folder, but inside tools/sub_folder I get "Import can not be resolved" error inside the notebook and the python file when I try to import from other_module.

MrYutz · 2022-09-15T11:59:42Z

I can confirm that pre-release 2022.9.21 fixed the local import issue for me. The only action performed on my end was a reload of VS-Code in an existing workspace.

torext · 2022-09-15T13:24:25Z

This still isn't fixed for me when I create a new blank unsaved Jupyter notebook via Create: New Jupyter Notebook. In that case I still have the same exact behaviour as shown in the GIF in #3017 (comment)

Below shows the failure in a new notebook and how it's now working in a saved notebook. Also, I keep getting double entries in the autocomplete suggestions regardless of whether I'm in a saved notebook or not:

If I set

"python.pylanceLspNotebooksEnabled": false,
"jupyter.pylanceHandlesNotebooks": false,

in the user settings, then both issues go away.

MrYutz · 2022-09-15T14:48:32Z

@torext I am having the duplication issue again after the update. It had gone away, but now I am getting duplicate symbol suggestions, but only for native python libraries. See screenshot. dict and dict.update() show duplicates, but none of the other recommendations are duplicated.

debonte · 2022-09-19T19:45:28Z

@elashrry, if conda develop is doing an editable install, this may be related to #3262. Can you please file a new issue?

@torext, @MrYutz, please file new issues for your recent comments. It's extremely difficult to track and discuss what you are seeing when it's posted as comments on closed issues.

torext · 2022-09-20T07:41:14Z

@torext, @MrYutz, please file new issues for your recent comments. It's extremely difficult to track and discuss what you are seeing when it's posted as comments on closed issues.

The main message of my comment was that the issue under discussion is still not fixed when opening a new notebook. Should I file a new issue for this?

elashrry · 2022-09-20T13:17:17Z

@elashrry, if conda develop is doing an editable install, this may be related to #3262. Can you please file a new issue?

Thank you. I created this issue #3365

debonte · 2022-09-20T15:28:42Z

The main message of my comment was that the issue under discussion is still not fixed when opening a new notebook. Should I file a new issue for this?

@torext, yes please. Pylance handles unsaved notebooks differently than saved notebooks.

Also, I think the completion duplication issue is unrelated. It may be microsoft/vscode-jupyter#11038 as you suggested. I'm not sure.

svenstehle · 2022-09-21T16:47:32Z

@torext

I can confirm this. Setting "python.pylanceLspNotebooksEnabled": false, in user-settings solves the local import issue for me with the current release VSCode 1.71.2 and Pylance v2022.9.20

debonte · 2022-09-22T00:31:46Z

@svenstehle, FYI we will be removing the old notebooks implementation in the future, at which point the "python.pylanceLspNotebooksEnabled": true behavior will be the only option. So setting it to false is only a temporary workaround. If you're having problems in the latest version of Pylance that require you to disable LSP notebooks, please provide details (in a new issue).

dlefcoe · 2022-11-28T23:36:17Z

python

what do you mean "in the user settings". where are the user settings or how does one get to the user settings that you are referring to ?

elashrry · 2022-11-29T08:50:34Z

@dlefcoe You open the Command Palette by the keyboard shortcut: Command+Shift+P on mac and Ctrl+Shift+P on windows, then write "user settings", you should find user settings as GUI and user settings as JSON. Choose what you prefer.
JSON is easier so that you can copy the settings people are referring to as they wrote them.
In the GUI option, you can search for what you want.

archongum · 2023-03-30T04:15:01Z

Clean cache > Python: Clear Cache and Reload Window works for me.
Ref: https://stackoverflow.com/a/74177108/9756912

thiswind · 2023-07-01T06:44:23Z

Clean cache > Python: Clear Cache and Reload Window works for me.
Ref: https://stackoverflow.com/a/74177108/9756912

Great! It works for me!

zhong-yy · 2024-05-03T11:36:33Z

Weird behaviour!!!

github-actions bot added the triage label Jul 8, 2022

debonte self-assigned this Jul 11, 2022

judej added the needs investigation Could be an issue - needs investigation label Jul 11, 2022

github-actions bot removed the triage label Jul 11, 2022

judej mentioned this issue Jul 13, 2022

"Import could not be resolved" for local packages and modules #3035

Closed

debonte added the lsp notebooks label Jul 18, 2022

heejaechang mentioned this issue Jul 25, 2022

Pyright no longer resolves modules in the directory containing notebooks #3088

Closed

Nufflee mentioned this issue Aug 3, 2022

[Bug] Duplicated suggestions, typehints, docs etc. #3027

Closed

heejaechang self-assigned this Aug 4, 2022

heejaechang added fixed in next version (main) A fix has been implemented and will appear in an upcoming version and removed needs investigation Could be an issue - needs investigation labels Aug 4, 2022

heejaechang closed this as completed Aug 8, 2022

judej reopened this Aug 16, 2022

judej unassigned debonte Aug 16, 2022

OllieKampo mentioned this issue Aug 18, 2022

Unexpected pylance "reportMissingImports" in notebook for local package #3208

Closed

bschnurr closed this as completed Aug 25, 2022

torext mentioned this issue Sep 15, 2022

Opening Interactive window results in duplicates in the symbols list (suggestions, autocomplete, ...) microsoft/vscode-jupyter#10846

Closed

2 tasks

torext mentioned this issue Sep 16, 2022

Intellisense completions have duplicates when python.pylanceLspNotebooksEnabled is true microsoft/vscode-jupyter#11038

Closed

byehack mentioned this issue Oct 25, 2022

Duplicate Results for python files when jupyter.pylanceHandlesNotebooks is true microsoft/vscode-jupyter#11780

Closed

wondrive mentioned this issue Oct 28, 2022

The Pylance server crashed 5 times in the last 3 minutes wondrive/errors#4

Open

torext mentioned this issue Nov 8, 2022

Jupyter notebook IntelliSense doesn't autocomplete modules in workspace subfolders when "python.pylanceLspNotebooksEnabled": true #3177

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Import can not be resolved error in pylance jupyter notebook for importing .py file in same directory as notebook #3017

Import can not be resolved error in pylance jupyter notebook for importing .py file in same directory as notebook #3017

jj-github-jj commented Jul 8, 2022 •

edited

Loading

vvvv0208 commented Jul 11, 2022

debonte commented Jul 11, 2022

laye0619 commented Jul 12, 2022 •

edited

Loading

Nufflee commented Jul 15, 2022 •

edited

Loading

laye0619 commented Jul 15, 2022

jj-github-jj commented Jul 20, 2022

heejaechang commented Aug 8, 2022

Yura52 commented Aug 15, 2022

ccrvlh commented Aug 16, 2022

MrYutz commented Aug 18, 2022 •

edited

Loading

Xabitsuki commented Aug 25, 2022

YDX-2147483647 commented Aug 25, 2022

bschnurr commented Aug 25, 2022

Michaelzhouisnotwhite commented Sep 2, 2022

torext commented Sep 9, 2022 •

edited

Loading

antonioalegria commented Sep 13, 2022 •

edited

Loading

MrYutz commented Sep 13, 2022

debonte commented Sep 13, 2022

debonte commented Sep 15, 2022

elashrry commented Sep 15, 2022 •

edited

Loading

MrYutz commented Sep 15, 2022 via email •

edited

Loading

torext commented Sep 15, 2022 •

edited

Loading

MrYutz commented Sep 15, 2022

debonte commented Sep 19, 2022

torext commented Sep 20, 2022 •

edited

Loading

elashrry commented Sep 20, 2022

debonte commented Sep 20, 2022

svenstehle commented Sep 21, 2022

debonte commented Sep 22, 2022

dlefcoe commented Nov 28, 2022

elashrry commented Nov 29, 2022

archongum commented Mar 30, 2023

thiswind commented Jul 1, 2023 •

edited

Loading

zhong-yy commented May 3, 2024

Import can not be resolved error in pylance jupyter notebook for importing .py file in same directory as notebook #3017

Import can not be resolved error in pylance jupyter notebook for importing .py file in same directory as notebook #3017

Comments

jj-github-jj commented Jul 8, 2022 • edited Loading

Environment data

Code Snippet

Expected behavior

Actual behavior

Logs

vvvv0208 commented Jul 11, 2022

debonte commented Jul 11, 2022

laye0619 commented Jul 12, 2022 • edited Loading

Nufflee commented Jul 15, 2022 • edited Loading

laye0619 commented Jul 15, 2022

jj-github-jj commented Jul 20, 2022

heejaechang commented Aug 8, 2022

Yura52 commented Aug 15, 2022

ccrvlh commented Aug 16, 2022

MrYutz commented Aug 18, 2022 • edited Loading

Xabitsuki commented Aug 25, 2022

YDX-2147483647 commented Aug 25, 2022

bschnurr commented Aug 25, 2022

Michaelzhouisnotwhite commented Sep 2, 2022

torext commented Sep 9, 2022 • edited Loading

antonioalegria commented Sep 13, 2022 • edited Loading

MrYutz commented Sep 13, 2022

debonte commented Sep 13, 2022

debonte commented Sep 15, 2022

elashrry commented Sep 15, 2022 • edited Loading

Update

MrYutz commented Sep 15, 2022 via email • edited Loading

torext commented Sep 15, 2022 • edited Loading

MrYutz commented Sep 15, 2022

debonte commented Sep 19, 2022

torext commented Sep 20, 2022 • edited Loading

elashrry commented Sep 20, 2022

debonte commented Sep 20, 2022

svenstehle commented Sep 21, 2022

debonte commented Sep 22, 2022

dlefcoe commented Nov 28, 2022

elashrry commented Nov 29, 2022

archongum commented Mar 30, 2023

thiswind commented Jul 1, 2023 • edited Loading

zhong-yy commented May 3, 2024

jj-github-jj commented Jul 8, 2022 •

edited

Loading

laye0619 commented Jul 12, 2022 •

edited

Loading

Nufflee commented Jul 15, 2022 •

edited

Loading

MrYutz commented Aug 18, 2022 •

edited

Loading

torext commented Sep 9, 2022 •

edited

Loading

antonioalegria commented Sep 13, 2022 •

edited

Loading

elashrry commented Sep 15, 2022 •

edited

Loading

MrYutz commented Sep 15, 2022 via email •

edited

Loading

torext commented Sep 15, 2022 •

edited

Loading

torext commented Sep 20, 2022 •

edited

Loading

thiswind commented Jul 1, 2023 •

edited

Loading