UndefinedVariable in interactive window

[stevenlis]

Environment data

• Language Server version: Pylance v2023.2.20
• Jupyter extension: v2023.1.2010391206
• OS and version: macos 13.2 (22D49)
• Python version (& distribution if applicable, e.g. Anaconda): 3.9.12

Version: 1.75.1
Commit: 441438abd1ac652551dbe4d408dfcec8a499b8bf
Date: 2023-02-08T21:34:01.965Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: 10.2.154.23-electron.0
OS: Darwin arm64 22.3.0
Sandboxed: No

Code Snippet

XXX

Repro Steps

I have also tried with the pre-release of Jupyter extension

Expected behavior

XXX

Actual behavior

XXX

Logs

log.txt

XXX

microsoft/pylance-release#3661

[debonte]

Thanks. I'm able to repro this now. Not sure why I wasn't able to before.

It's interesting that df is shown in the completion list, but still flagged as undefined.

[philnagel]

Also experiencing this issue, seeing it both on my M1 Mac and a Windows machine. Let me know if there's any info I can provide to help troubleshoot.

[rogerlga]

Thanks for directing me to this issue. I'm also facing the same problem above, as I reported here: #6987 (comment).
My versions:

vscode: 1.76.0
Python extension: v2023.4.0
Pylance extension: v2023.3.10
Jupyter extension: v2023.2.1000592019

[debonte]

This is a bug in the Jupyter extension. I'll send a PR shortly.

[stevenlis]

Hi, @debonte. Thanks for the fix. I've seen many updates of Jupyter extension. Will this be included in the next update soon?

[debonte]

@StevenLi-DS, the fix is currently available in Jupyter's prerelease builds. It should appear in their release builds in a couple weeks. I believe that, aside from hotfixes, new stable builds of Jupyter are typically released to the public on the first Thursday of each month.

You could watch the Python blog for the April release announcement, similar to this one from March: https://devblogs.microsoft.com/python/python-in-visual-studio-code-march-2023-release/

[stevenlis]

@debonte I just realized that I've been using the prerelease builds for weeks. The problem still exists in v2023.3.1000830504 somehow.

[debonte]

I can't repro it with that version. Could you please set "python.trace.server": "verbose", repro it, and provide the resulting "Python Language Server" log?

Note that this setting is hidden, so you'll need to set it directly in the settings.json rather than via the Settings UI.

[stevenlis]

@debonte I couldn't find the settings, but I did set "python.analysis.logLevel": "Trace"

jupyterlab: v2023.3.1000851011
pylance: v2023.3.30

vscode-log.log

[debonte]

I couldn't find the settings...

Ctrl+Shift+P to open the command palette. Then search for "Preferences: Open User Settings (JSON)". Execute that command and it will open your user settings.json. Add "python.trace.server": "verbose" in there.

We need to enable this to be able to see the LSP message traffic.

[stevenlis]

@debonte I think it's just hidden from the UI, but still in the json file... I see...

vscode-log.txt

[debonte]

@StevenLi-DS, thanks for the log. I'm able to repro this now and will investigate.

[debonte]

@StevenLi-DS, the second issue is now fixed. Please give it a try in the next Jupyter prerelease build.

[stevenlis]

@debonte Is there any chance there could be an official release to fix this annoying issue rather than waiting antoher month since the pre-release is having issue:

Can't install pre-release version of 'ms-toolsai.jupyter' extension because it is not compatible with the current version of Visual Studio Code (version 1.77.2).

[debonte]

@StevenLi-DS, I believe that the pre-release Jupyter builds require VS Code Insiders.