pylance-release
pylance-release copied to clipboard
parse error on magic statement on ipython mode.
When I open an. ipynb file using vscode, it always generates strange errors. Clearly able to operate normally.
The meaning of this error is "should be an expression".
Unable to import 'requests' from source parsing
I am using the latest version of VScode that comes with Pylance.
Pylance version:v2024.4.1
vscode version: 1.88.1 (user setup)
提交: e170252f762678dec6ca2cc69aba1570769a5d39
日期: 2024-04-10T17:41:02.734Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Windows_NT x64 10.0.22631
sounds like our tokenzier/parser is not ignoring % statement properly in ipython mode.
for requests, it is complaining that you didn't install requests packages in the openvino env.
sounds like our
tokenzier/parseris not ignoring%statement properly in ipython mode.for
requests, it is complaining that you didn't installrequestspackages in theopenvinoenv.
I have install requests and it can running success.
I have install requests and it can running success.
how about providing us a log to see what python paths (libraries) we got? if you are using latest pylance (104), then there should be Pylance: start logging/stop logging command.
can you provide us the log produced by the command to us?
The requests problem might be a dupe of this issue: https://github.com/microsoft/vscode-jupyter/issues/15965
Meaning we don't know which kernel is selected.
The log should show that though.
sounds like our
tokenzier/parseris not ignoring%statement properly in ipython mode.for
requests, it is complaining that you didn't installrequestspackages in theopenvinoenv.
It seems to be that it doesn't detect my openvino environment correctly. I'm using a virtual python environment under conda.
so, it probably is the dup of the bug Rich linked, then.
@heejaechang @rchiodo After reading your reply, it may have been caused by a kernel link error, so I tried switching the kernel multiple times and restarted VSCode and Windows 11. The error regarding import has disappeared now, it seems that the link is correct. But the first mistake still exists.
I put %pip install -q "matplotlib>=3.4" outside and it won't report any errors.
ya, first issue looks like this
sounds like our tokenzier/parser is not ignoring % statement properly in ipython mode.
looks like there is a bug around this - https://github.com/microsoft/pyright/blob/main/packages/pyright-internal/src/parser/tokenizer.ts#L450