VSCodium
Add instructions for PyLance workaround.
Microsoft prevents PyLance language server from running in unofficial builds, but an easy workaround is to modify product.json.
See #892.
I added instructions to the Docs.
As Jedi is always enabled if Pylance is not found wouldn't it be most reasonable to just uninstall/disable PyLance?
I don't have any setting for this done, so it is on Default and when checking the Output Pane, Python group the very first item says:
Starting Jedi language server.
I think adding a link to the workaround (or simple instructions to do so) in the "Replacements" section could be appropriate as Pylance is already stated there as only partially compatible.
Also please refer: https://github.com/VSCodium/vscodium/issues/940#issuecomment-1341932901
Hello Sebastian!
I'm wondering if this method of using Pylance in VSCodium still works.
For Linux, you mentioned the directory: /home/
I'm closing this PR. Feel free to open a discussion if you want further talks.
The best solution is to have an open alternative for PyLance instead of trying the make a closed-source extension works...
It looks like this no longer works as of version 2023.8.20.
Yeah, apparently starting from this version the product.json trick is not longer enough... 😭
If anyone still wants to bother with Pylance, the last working version can be found here.
https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ms-python/vsextensions/vscode-pylance/2023.6.40/vspackage
No need for the product.json trick. Just install VSCodium, install the extension and you are ready to go.
Save it on your drive! Who knows for how long M$ will keep that link up.
The checksum for the file for posterity.
Name: ms-python.vscode-pylance-2023.6.40.vsix Size: 13884740 bytes (13 MiB) SHA256: 2799d1a108d454a68caacd10245634bf3bad8d667d747e8eec55c8f996486814 SHA1: 832b3ad87e042497a99156f7c7b07717f734c9f0 BLAKE2sp: 089240601221b6fecd13991490c925ac2f11b9ec51e96bd9b00dbbccfde151b7
Would it be reasonable to distribute that as a built-in extension by including it in the patchset or do we know/guess that this is/will soon be broken? The only possible downside I currently see are 12 MB...
If anyone still wants to bother with Pylance
Strangely I couldn't find any reasonable data source on differences between Pylance and Pyright (we all know that Pylance is based on Pyright). Does anybody have a clue?
Actually there is some information in Pylance FAQ:
What features are in Pylance but not in Pyright? What is the difference exactly?
Pylance has a handful of valuable features that are not available in Pyright, including semantic highlighting, refactoring code actions (extract variable/extract method), docstrings for built-in/standard library modules, and IntelliCode compatibility. Pylance also ships with a collection of type stubs for popular modules to provide fast and accurate auto-completions and type checking.
Would it be reasonable to distribute that as a built-in extension by including it in the patchset or do we know/guess that this is/will soon be broken?
No! VSCodium doesn't add features compared to Visual Studio Code. Also PyLance is closed-sourced and can be installed only with MS products (https://marketplace.visualstudio.com/items/ms-python.vscode-pylance/license)