Semantic highlighting for Python: Pylance issue 2023

[finnlogin]

Hi!
I have a problem with semantic highlighting in VSCodium (screenshot: VSCodium is on the left, VSCode is on the right). I have the same issue on MacOS and Linux Mint. After research, I found out that it has to do with the fact that Microsoft prevents PyLance language server from running in unofficial builds. In this thread there is a solution; however, it seems outdated because it doesn't work anymore.

Has anyone encountered this issue and managed to find a solution?

[EndlessFractal]

Link to the last working version:

https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ms-python/vsextensions/vscode-pylance/2023.6.40/vspackage

Works perfectly as of writing. Just install it manually by going to extensions, click on the 3 dots and click on Install from VSIX, and select the downloaded file.

[finnlogin]

It works for me too!
You're my savior! Thanks a bunch!

[ovo-Tim]

Do we have any other options？We can't use old version for ever. 😢

[finnlogin]

You can replace the version of the extension in the provided link with the latest one.
https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ms-python/vsextensions/vscode-pylance/2023.8.20/vspackage

[EndlessFractal]

You can replace the version of the extension in the provided link with the latest one. https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ms-python/vsextensions/vscode-pylance/2023.8.20/vspackage

I've tested the 5 most recent versions (2023.8.21, 2023.8.20, 2023.8.11, 2023.8.10, 2023.7.43) and none work.

Until someone finds a workaround, the last known working version (2023.6.40) will have to do.

A screenshot of the latest VSCodium running the latest Pylance, notice that the color highlighting does not work.

Edit: @burritosoftware this might be of interest to you.

Cheers!

[finnlogin]

You can replace the version of the extension in the provided link with the latest one. https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ms-python/vsextensions/vscode-pylance/2023.8.20/vspackage

I've tested the 5 most recent versions (2023.8.21, 2023.8.20, 2023.8.11, 2023.8.10, 2023.7.43) and none work.

Until someone finds a workaround, the last known working version (2023.6.40) will have to do.

A screenshot of the latest VSCodium running the latest Pylance, notice that the color highlighting does not work.

Edit: @burritosoftware this might be of interest to you.

Cheers!

You're right! I downloaded and installed the latest version but never tested it. I'm sorry for misleading you guys.

[awsms]

Thanks so much for the link @EndlessFractal, I tried everything, assuming it was an issue on my end. 🥲
Do you know if that's Microsoft enforcing the usage of their own extensions to proprietary VSCode-only, like they have done with the Copilot integration, the C# debugger etc?

[EndlessFractal]

Thanks so much for the link @EndlessFractal, I tried everything, assuming it was an issue on my end. 🥲 Do you know if that's Microsoft enforcing the usage of their own extensions to proprietary VSCode-only, like they have done with the Copilot integration, the C# debugger etc?

It is very possible, as they have taken measures in preventing its usage on the later versions, #935 shows this, as the previous trick of modifying the product.json no longer works.

[sergei-dyshel]

Hoping some another product.json trick is possible, I tried replacing entire file with the file from MS VScode and Pylance still didn't work 😭 Bye bye semantic highlighting and other goodies....

[Rantunah]

I went to check out the console for the Python Language Server with the Microsoft extensions and I got this:

2023-09-05 18:24:57.301 [info] (Client) You may install and use any number of copies of the software only with Microsoft Visual Studio, Visual Studio for Mac, Visual Studio Code, Azure DevOps, Team Foundation Server, and successor Microsoft products and services (collectively, the “Visual Studio Products and Services”) to develop and test your applications. The software is licensed, not sold. This agreement only gives you some rights to use the software. Microsoft reserves all other rights. You may not: work around any technical limitations in the software that only allow you to use it in certain ways; reverse engineer, decompile or disassemble the software, or otherwise attempt to derive the source code for the software, except and to the extent required by third party licensing terms governing use of certain open source components that may be included in the software; remove, minimize, block, or modify any notices of Microsoft or its suppliers in the software; use the software in any way that is against the law or to create or propagate malware; or share, publish, distribute, or lease the software (except for any distributable code, subject to the terms above), provide the software as a stand-alone offering for others to use, or transfer the software or this agreement to any third party.

So I guess that this might be Microsoft's attempt to enforce the license terms and force some users into VSCode.

[awsms]

I tried all the builds (2023.6.x up to 2023.8.x), and 2023.8.10 is the last build that works for me. Wondering why it didn't work for you @EndlessFractal