You are not logged in.

#1 2022-02-10 20:36:36

jurc192
Member
Registered: 2019-10-26
Posts: 3

vscode + python - no suggestions. Intellisense not working?

I have vscode (from community repo) installed, using it for python development.
It seems like the language seriver or intellisense are not working, since no suggestions are shown when pressing CTRL+SPACE.
How can I debug this? Where to start looking for the issue?

vscode version: 1.64.0
pacman package: community/code 1.64.0-1
VSCode extensions installed and enabled:
- python v2022.0.1814523869
- pylance v2022.2.1

Offline

#2 2022-02-11 07:00:07

ishaanbhimwal
Member
Registered: 2022-01-21
Posts: 48
Website

Re: vscode + python - no suggestions. Intellisense not working?

Which language server are you using? See what you have for "python.languageServer" setting. It should be either default or pylance.

Last edited by ishaanbhimwal (2022-02-11 07:00:55)

Offline

#3 2022-02-11 11:09:22

jurc192
Member
Registered: 2019-10-26
Posts: 3

Re: vscode + python - no suggestions. Intellisense not working?

I am using 'default', so that would be pylance. However, if I try to switch to 'Jedi' I do get (some kind of) suggestions...

Offline

#4 2023-09-17 09:06:21

ali_molaei
Member
From: Iran
Registered: 2015-12-24
Posts: 63
Website

Re: vscode + python - no suggestions. Intellisense not working?

Same problem here, I have suggestions using jedi, but not pylance, did you ever solved the problem? @jurc192

Offline

#5 2023-10-01 03:43:07

spacekobold
Member
Registered: 2022-11-19
Posts: 14

Re: vscode + python - no suggestions. Intellisense not working?

Pylance is (most unfortunately) a Microsoft proprietary extension and they restrict it from running on non-official builds, which the Arch repo's code package is. If you want to use the Pylance extension, you'll probably have to use Microsoft's official build. There's an AUR package (visual-studio-code-bin) if you value having a good Python language server over keeping Microsoft telemetry off of your system. There is/was a way to get around this by editing some lines in the product.json file for non-official builds (e.g. for vscodium, it's /usr/share/vscodium/resources/app/product.json), but in my experience it seems like this was patched for the newest versions of the Pylance extension. https://www.flypenguin.de/2023/02/26/us … rketplace/

Offline

Board footer

Powered by FluxBB