-
Notifications
You must be signed in to change notification settings - Fork 770
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Developer: inspect editor tokens and scopes #4924
Comments
I'm unable to repro this. Can you please set |
Have put
Hovered over a function from which I'd guess the first log came, then clicked on the function and lastly through F1 ran |
After turning Pylance back off got this doing the same actions:
This worked fine and could see the information. |
By "off", do you mean that you switched to Jedi?
Are you not seeing a response to this semantic tokens request? On my machine, I see the following:
|
With off I mean disabling Pylance, after which the only extensions that I have and are enabled are Flake8, Python and WSL.
|
Ok. With the Pylance extension disabled and Can you please re-enable the Pylance extension, reproduce the problem, and provide the resulting full "Python Language Server" log? If it's too large to include in the text of a comment, you can copy it to a file and drag that file into the comment as an attachment. |
Right so about one to two days ago my friend who had the same problem said that their syntax checking and variable colours had returned, though it was "not fast" like showing up when typing (I assume). Now when I enabled Pylance again I was not able to reproduce the problem. |
The default is
Is VS Code prompting you to reload with a "Reload Required" button on Pylance in the extension pane? The contents of text.txt are either not the full "Python Language Server" log or not from Pylance (i.e. Jedi is still running instead). |
No reload was required when I enabled Pylance. |
For whatever reason your last response wasn't showing up until I commented myself. |
I'm still unable to reproduce this. Can you see if it repros for you on the most recent prerelease build of Pylance (2023.12.102)? |
This issue has been closed automatically because it needs more information and has not had recent activity. If the issue still persists, please reopen with the information requested. Thanks. |
Type: Bug
Developer: inspect editor tokens and scopes does not work when the Pylance extension is enabled.
Don't know if the rest of my extensions will be sent with this report but just to be sure I have Flake8, Python and WSL installed as extensions.
Opened a .py file from a wsl folder (not well versed enough to know if that is an accurate description but it's the best I can do) and tried to run the command 'Developer: Inspect Editor Tokens and Scopes' but did not work. Ran extension bisect to find that the 'Pylance' extension was at fault. Can still code fine without it so not to worried about knowing if it gets fixed. This is all I know, hope this helps :)
Extension version: 2023.10.10
VS Code version: Code 1.83.0 (e7e037083ff4455cf320e344325dacb480062c3c, 2023-10-03T16:12:16.321Z)
OS version: Windows_NT x64 10.0.19045
Modes:
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
A/B Experiments
The text was updated successfully, but these errors were encountered: