vscodium: current ms-python won't install under VSCodium (mstoolsai.jupyter incompatibility)
Describe the bug The official VSCode Python extension fails to install under VSCodium. Downloading the files from the Marketplace and manually from the GitHub repo shows an identical error about the extension not being compatible with the current version of VSCode. This happens even with older versions being downloaded directly via the GitHub releases page for the extension, which can be found here.
Please confirm that this problem is VSCodium-specific
- This bug doesn’t happen if I use Microsoft’s Visual Studio Code. It only happens in VSCodium.
Please confirm that the issue/resolution isn’t already documented
- I checked the Docs page and my issue is not mentioned there.
To Reproduce Steps to reproduce the behavior:
- Install the official ms-python extension from the Marketplace and observe the install failing OR
- Download the latest VSIX installer of the ms-python extension from https://github.com/microsoft/vscode-python/releases
- Open the Command Palette and run the
Extensions: Install from VSIX...command - Locate the file downloaded from the GitHub repo and attempt to install it
- Observe the install failing
Expected behavior The extension should install, even if it only works via a manual download
Screenshots
Desktop (please complete the following information):
- OS: Windows 10, version 20H2
- Architecture: x64
- Version 1.59.1
Additional context PS: If you care about Python being supported on VSCodium, please upvote this issue where a user is petitioning Microsoft to add their Python extension to the Open VSX Repo. Thanks in advance!
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 13
- Comments: 29 (10 by maintainers)
The issue seems to be fixed in the futur
VSCodium v1.60Looks like a known bug, seems to only work on “insiders” currently: https://github.com/microsoft/vscode-python/issues/17296
@GitMensch I’ve added the fact you pointed out to the wiki compatibility page.
Please remember that the default installation of the python plugin in VSCode is not free since May 2021 any more, as it automatically installs and uses Pylace, an extension that MS explicit told will not be available under a free license. The “good” thing here: if the Pylace extension is not available (disabled or cannot be auto-installed like in the case of Open-VSX as extension provider) then the free language support is still activated. I guess that MS will not put very much efforts to improve the free language support in the future, but one could still try to PR missing features (I hope that they don’t deprecate that too soon).
So in the comparison of VSCode + Python against any build of vscode + Python: please always deactivate the Pylace extension in VSCode and restart it, then compare. @mariobrostech If you do this, are the turtle commands still “properly handled” in VSCode? If yes: please create a new issue with the details.
I’m closing this one as the installation now works.
Ya, it’s weird! Just switching to Visual Studio Marketplace is fixing the issue. So I guess I was wrong…
In the meantime, I managed to make it work. Keep in mind that this is by no means a long term solution. But, if someone needs this to be working exactly right now (like me), it may be a temporary solution. Here, there’s a way to use the actual VS Code marketplace, instead of open-vsx. You just need to make a “new” product.json in a specific folder (depends on your OS).
Some considerations: