Solution to Pylance not working with VSCodium

[felix9743]

Hi everybody, like you, when version 2023.8.20 of Pylance was released, the bypass trick no longer worked and given that I was on vacation, I had thought that someone would find a new solution. But today, we are at version 2023.9.10 (and VSCodium 1.82.2) and it seems to me that there is still no reliable solution to solve the problem...

So, I rolled up my sleeves and I tested again and again... Until when fiddle the files of the extension itself, I managed to make it work again! This method is terribly stupid and not the most convenient, but it worked on 3 of my computers with different configurations and it has the advantage of not need to change the name of the application anymore.

So to make it simple, here are the changes to be made to be able to install the extension and remove the verification (I only have Windows, but it should be the same under Linux and I don't know for MAC):

1. Edit the C:\Program Files\VSCodium\resources\app\product.json or create a product.json in C:\Users\YOUR_USERNAME\AppData\Roaming\VSCodium

2. Set the values of extensionsGallery with:

	"extensionsGallery": {
		"serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
		"cacheUrl": "https://vscode.blob.core.windows.net/gallery/index",
		"itemUrl": "https://marketplace.visualstudio.com/items"
	}

3. Install the Pylance and Python extension. Close the VSCodium when finished.

4. Open this path C:\Users\YOUR_USERNAME\.vscode-oss\extensions\ms-python.vscode-pylance-2023.X.XX\dist\

5. Rename extension.bundle.js to extension.bundle.js.bak (backup).

6. Recreate a empty file extension.bundle.js (to make work the Jupyter extension).

---

Here, I hope it'll be useful to you. If someone wants to modify DOCS.md to put the explanations or highlight this discussion, it would be cool for the others users ^^

PS: Sorry for my english, I not have habitude to write in english.

[ThatIsAPseudo]

On macOS product.json is located in /Applications/VSCodium.app/Contents/Resources/app/product.json or in /Users/User/Library/Application Support/VSCodium/product.json and extension.bundle.js is in /Users/User/.vscode-oss/extensions/ms-python.vscode-pylance-2023.X.XX/dist

[pvares]

And on Linux (Ubuntu 20.04) they were in:

• ~/.config/VSCodium/product.json
• ~/.vscode-oss/extensions/ms-python.vscode-pylance-2023.9.10/dist/extension.bundle.js

[mdilena]

Thanks very much for this, it worked like a charm! Until they'll do something else to prevent it 😁

[chardoncs]

It works! Thank you folks!

[awsms]

thanks so much OP, wish it was that easy to get the C# debugger to work 🤣

[felix9743]

Sorry but I can't help too much for C# since I've never done one.

[fabifont]

Seems like they patched this workaround in version 2023.10.31

[NiklasMM]

Can confirm it doesn't work anymore in v2023.10.40. I guess it's time to finally switch to PyCharm.

[fabifont]

You can use the previous version or Pyright instead of Pylance

[Whyhow314]

Works fine for me in v2023.10.40, but not the prerelease v2023.10.41.

[an4s911]

I tried Pyright, but Pyright doesn't work when Python extension is turned on

[ykvch]

Now to make pylance work: Extensions -> pylance -> disable -> press "reload required".
After vscodium starts: Extensions -> pylance -> enable
Works until vscodium closed (then disable/enable has to be repeated). And python-specific rulers are not shown.

[skbeh]

To make 2023.10.50 work:

1. Remove extension.bundle.js.

In server.bundle.js:

2. Format the file (maybe with Prettier).
3. Search for _0x1128b5, and add return; to the start of the function found (like ['_enableJin' + _0x5f2a8a(0x1083) + 'y'](_0x1128b5) {).
4. Search for throw new Error(_0x3f799c[_0xcacf35(0x1664)+_0xcacf35(0x1803)]); (throw new Error(_0x3f799c.licenseErrorText);) and remove it.
5. Replace _0x2f33cc[_0x1efd68(0x1934) + _0x1efd68(0x135e)] with void 0x0.

Repack server.bundle.js, install the vsix and it should work.

[claviola]

@skbeh any tips for 2023.11.10?

[felix9743]

Hello, for information, this solution works for me with the latest versions:

• Windows 10 and VSCodium v1.84.2
• Python v2023.20.0 and Pylance v2023.11.10
• Jupyter v2023.10.11

PS: There were 1 or 2 versions where this tips no longer worked but strangely, it works again now....

[robotoshi]

Confirmed, your original solution works for me on Ubuntu 20.04.6 for Pylance 2023.11.10 and vscodium 1.84.2

Thanks so much for your work!

[felix9743]

😊

[CarterSnich]

4. Open this path `C:\Users\YOUR_USERNAME\.vscode-oss\extensions\ms-python.vscode-pylance-2023.X.XX\dist\`

5. Rename `extension.bundle.js` to `extension.bundle.js.bak` (backup).

6. Recreate a empty file `extension.bundle.js` (to make work the Jupyter extension).

Worked for VSCodium 1.84.2 | Pylance v2023.11.10

[CarterSnich]

Seems like that this discussion become active this past few weeks. I'm still on v2023.11.10 and OP's workaround still works for me perfectly fine.

[robotoshi]

Seems like it doesn't work anymore on the new Pylance version 2023.12.1 😢

[Oreeeee]

Yeah. It shows something that you need Visual Studio Code and that working around this limitation is violation of ToS. Downgrading also doesn't work.

[fabifont]

Downgrading to 2023.11.10 worked for me

[Oreeeee]

I'm running v2023.10.53 and it's still showing the error. Maybe the check is in the Python extension and not in Pylance?

Edit: Nope, still not working for me

[tstrose]

One observation I had is that the contents of the extensions folder for VSCode [on Windows this is usually in C:\Users[YOUR USERNAME].vscode\extensions can be copied (wholesale) and used in VSCodium/Cursor.

I have only tested this in Cursor (based on VSCode 1.85), but feel like it should work for VSCodium as well:

1. Have the Python and Pylance extensions installed in VSCode - either through the VSIX or the market place.
2. Copy the relevant extension folders and extensions.json from the .vscode folder to the .vscodium/extensions or .cursor/extensions folder.
3. Make the changes to product.json outlined in the OP.
4. Open VSCodium/Cursor. You will notice that it will have the complaint about Pylance and error out with Code: -32603. However after complaining, if you check the extensions folder, you will notice that it is attempting to download a prior version of Pylance/Python that does not error out (in Cursor as of the date of this post, this was Python 2023.22.1 & Pylance 2023.10.40)
5. Once finished, the Extensions tab will indicate that those extensions require a reload of the IDE.
6. Once reloaded, extensions.json should have been automatically updated to use the newly downloaded versions and you will observe that Pylance works.

Hope this helps someone as I accidentally deleted those newly downloaded versions of the extensions, since I had no idea where they came from, and spent the rest of the afternoon trying to figure out how I broke my Pylance in Cursor.

[fabifont]

Has anyone managed to make v2024.2 work?

[rob4226]

This "FOSS" editor but closed source extension game is getting annoying. What are some other viable options for Python extensions that could replace Pylance?

[fabifont]

I am actually using pyright

[Windows81]

Microsoft will hate me for this: https://gist.github.com/Windows81/0b4f28f47b25192ab372a156ca4ce6da

[Windows81]

Tested to Work on 2024.2.103; Windows

1. Download the Python extensions as .vsix files.
2. If you're running 2024.2.103, Put this file in C:\Users\USERNAME\.vscode-oss\extensions\ms-python.vscode-pylance-2024.2.103\dist\extension.bundle.js. I prettified the code and commented the verif*ckation stuff out (lines 8901-8956). It took me some hours.

[Fissium]

Doesn't work for me

[Windows81]

Heya. Can you send me a screenshot of the ms-python.vscode-pylance-2024.2.103\dist\ directory with the file sizes?

[Oreeeee]

Works for me, thanks

[rob4226]

@Windows81 That's a damn fine job. Thank you so much!!!

[Fissium]

@Windows81

Heya. Can you send me a screenshot of the ms-python.vscode-pylance-2024.2.103\dist\ directory with the file sizes?

[fabifont]

Working solution:

1. Install pylance normally from vscode extensions
2. Install prettier from vscode extensions
3. Open extension.bundle.js in vscode
4. Format the file using prettier
5. Search for })();, you will find a few entries
6. Pick the one that has })()) in the next line
7. Comment everything starting from the end of the return value (arrow in the first screen) under that line to the if at the top (second screen) (you can follow the last closed parentheses before the return statement and scroll up till you match the if)

Please don't look at other strings or variable names in the file because they always change since they are obfuscated.

[Oreeeee]

It would be much easier if you made a .patch file

[fabifont]

I never did one and every time the extension gets updated the file changes. Also, every user has a different obfuscation and Microsoft may add tracking calls under the hood.

[skbeh]

every user has a different obfuscation

The vsix every user got is same for a specific version.

Microsoft may add tracking calls under the hood.

They actually did. Just search "telemetry" in the deobfuscated code.

[kuolemaaa]

@skbeh May I ask what tool did you use to deobfuscate that js and find what block of code to disable ?

[daiyam]

Does anyone have tested https://open-vsx.org/extension/detachhead/basedpyright? Thx

[mattmess1221]

Basedpyright is a great alternative to pylance! It adds the typing features of pylance (semantic highlighting, inlay hints, import quick fixes, etc) that Microsoft doesn't want to upstream into pyright.

[pickx]

I wrote a Rust script that automatically finds the extension.bundle.js file and comments out the VSCode check.

Save the file, give it executable permissions (chmod +x) then execute it like a shell script. You would need a Rust nightly toolchain installed.

disclaimer: I've only tested it on my machine, and only on macOS (feedback welcome)

[alexlnkp]

Works FLAWLESSLY!
Thank you so much, kind man!

Arch x86_64, 6.8.7-arch1-1
Pylance v2024.4.1

A note for others who never worked with rust:
Follow instructions on https://rustup.rs/
Then, customize the install and select nightly build

[CarterSnich]

Why in Rust instead of Python?

[sergei-dyshel]

@pickx
Thanks for sharing! Your script worked for me with Pylance 2024.3.2 (previous version) but didn't work with 2024.4.1 (latest version) - complained that pattern not found.

[pickx]

thanks for testing. I came up with another strategy that works for all versions 2024.4.1-2023.12.1 (and possibly earlier)

[JJK-IO]

Thanks @pickx

[jackyhevey]

on mac, version 2024.4.1
perl -i -pe 's/if\(!_0x19.*?disposables.*?};//' ~/.vscode-oss/extensions/ms-python.vscode-pylance-2024.4.1/dist/extension.bundle.js

[alexspf]

Arch Linux 2024.4, unless a meteor falls to Earth, then I'd be using other distros too :p

1. Download the Pylance VSIX file here
2. Install it in Vscodium (extension bar > 3 dots >)
3. Install Prettier for formatting extension.bundle.js
4. Open the terminal and type: (adjust the path for your version of Pylance)

vscodium ~/.vscode-oss/extensions/ms-python.vscode-pylance-2024.4.102/dist/extension.bundle.js

6. Press Ctrl+Shift+P and type "format with" (then select Prettier).
7. As @Gurgarath suggested:

Search for:
stop: () => Promise["resolve"]

In my case, there are two occurrences (i choose second). Comment out the occurrence with an "if" statement later and comment out all if statements (comment before the ';' at the end).
8) restart vs codium and use pylance again
ps: pylance dont show in extensions for me, but works now, thanks for help guys

[Windows81]

Heya. Would you be able to provide an example of the modified extension.bundle.js? I'm assuming that your exact script will work on all Windows and GNU/Linux systems.

[alexspf]

I use the second occurrence like the print

[skieop]

I use the second occurrence like the print

Thanks so much! Worked :)

[Gurgarath]

Warning: Pre-Release 2024.4.104 has added a few checks or changed the method, commenting the part we usually did doesn't work anymore

[skieop]

Absolute assholes, fuck Microsoft.

[rob4226]

It's time to move this discussion elsewhere: https://discord.gg/X5Aq73fV39

[fabifont]

Tbh it won't change anything

[Windows81]

@rob4226: I don't think that we should use Discord. The thread won't be vieweable on search engines anymore. Discord requires an account for solutions to be viewed at all.

If this discussion moves to Discord, I will forward anything I find over to GitHub. I will not do it the other way 'round.

[rob4226]

@Windows81 Ok boss

[iiPythonx]

I know it's less then ideal, but downloading 2024.4.102, installing it, and patching it (following #1641 (comment), or using #1641 (comment)) still works until the latest version can get figured out.

[LucasWolfgang]

The fixes above do not work with newer versions of pylance (tested using ms-python.vscode-pylance-2024.5.103), but using a newer version of vscodium and applying these fixes while using version 2024.4.102 do work well.

[renyuneyun]

Not sure if it's relevant, but I came across this post discussing a problem in the open-source version (of the extension, though in isort): microsoft/vscode-isort#316 (comment)
The "solution"/workaround is the same: use the official/MS version.

[ntluong95]

Any news for the newest version of Pylance?

[blipk]

I spent a while trying to patch it but it looks like they're now doing some kind of verification on the bundled extension file so the extension doesnt load if it's changed at all, and possibly some kind of remove verification as well.

If anyone else want to try searching for the string "licenseErrorText" and "generateVerificationString" in extension.bundle.js will lead you down the rabbit hole of relevant functions.

Any patches are probably going to be pretty fragile though.

Bunch of morons over there at MS trying to buy out the python ecosystem.

I decided I'm just going to use jedi

[ethanc8]

What about basedpyright? It uses a lot of Pylance's codebase, but the maintainer is not hostile to bug reports like Microsoft is, and it's improving its language server a lot

[ethanc8]

It looks like basedpyright is trying to reimplement Pylance's features and also provide better typechecking. If you just want a Pylance alternative, you can install the basedpyright extension and set basedpyright.analysis.typeCheckingMode to off. If there are any Pylance features you're missing, I might look into trying to implement them in basedpyright (some code in coc-pyright might be useful for this). In other news, upstream Pyright has become actively hostile to bug reports, which was at least one of the reasons why basedpyright started.

[ethanc8]

You should disable the Pylance extension and restart VSCode/VSCodium/code-oss before attempting to install basedpyright.

[ethanc8]

If there's anything you're missing, you might want to report it here and also at basedpyright's issues.

[sova2007]

To disable type output in basedpyright, how should one proceed?

Already installed.
"basedpyright.analysis.typeCheckingMode": "off"
Doesn't help.

[q-wertz]

Maybe check out "basedpyright.disableLanguageServices"

[ethanc8]

Maybe check out "basedpyright.disableLanguageServices"

That would completely disable the nice features

[Whyhow314]

Try setting editor.inlayHints.enabled to off

[sova2007]

Thank you all for your help.
This is a working option:

"basedpyright.analysis.typeCheckingMode": "off",
"editor.inlayHints.enabled": "off"

[WyattAutomation]

Thank you all for your help. This is a working option:

"basedpyright.analysis.typeCheckingMode": "off", "editor.inlayHints.enabled": "off"

This one worked for me. VS Codium, Ubuntu 22.04, Basedpyright extension

Crazy something as mundane as syntax highlighting gets screwed up. Oh well at least this works

[Oreeeee]

I don't really like Based Pyright. According to it, my entire codebase is a giant error, but actually I've been using it in production for a few months.

[ethanc8]

You should reduce the type checking level. "basedpyright.analysis.typeCheckingMode": "off",
"editor.inlayHints.enabled": "off"

[xjzh123]

Do you use the same config for basedpyright as that for pylance? Maybe it is because you have different config

[willfliaw]

I’ve tried both Pylance and Based Pyright, but I couldn’t get them to work as expected with Jupyter Notebooks. For instance, unused modules are not flagged as such, and other expected hints seem to be missing. Has anyone else experienced similar issues or found a reliable workaround?