parse error on magic statement on ipython mode. about pylance-release HOT 9 OPEN

The requests problem might be a dupe of this issue:
microsoft/vscode#199800

Meaning we don't know which kernel is selected.

The log should show that though.

from pylance-release.

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.

It seems to be that it doesn't detect my openvino environment correctly. I'm using a virtual python environment under conda.

from pylance-release.

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.

from pylance-release.

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.

I have install requests and it can running success.

from pylance-release.

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?

from pylance-release.

so, it probably is the dup of the bug Rich linked, then.

from pylance-release.

@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.

pyright-18848-KKlrxNNpgVLY.zip

from pylance-release.

I put %pip install -q "matplotlib>=3.4" outside and it won't report any errors.

from pylance-release.

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

from pylance-release.