Language Server Issues

What’s up with Pylance not being available in the marketplace? I’ve had similar problems (and more, since I’m using micropython) since I switched computers and the new one doesn’t have Pylance. Is there any way to make it work?

I’ve been experiencing:

  • Missing micropython library.
  • Folder error when trying to serve in the microcontroller folder.
  • “Python not installed” even though it is. Probably because the MicroPico extension recommends installing Pylance and apparently it defaults to Python in the marketplace search.
  • Python extension detects a server conflict and sets the workspace to PythonServer:None. While this works for Cursor, this breaks the project in vanilla VSCode, making it difficult to use it in other computers or remedy the previous items by switching back and forth.

I can’t recall other errors, but was left with the impression that Micropython and Pylance simply worked better in general

@ravirahman I haven’t resolved the issue, the VSCode base used by 1.2 uses a different mechanism for configuring a custom marketplace.

These instructions do not work either on Cursor 1.2:
https://github.com/VSCodium/vscodium/blob/master/docs/extensions.md#how-to-use-a-different-extension-gallery

Is there no way to change the marketplace in 1.2?
(The settings in 1.2 only lets you override the service url, there are other fields that are required to be overridden so that doesn’t work on its own)

1 Like

I think i’m a little closer to figuring out my error. All errors that spawn from the broken thing have this “basedpyright” tag next to the error name. Is this expected behavior? I have the Anysphere “Python” extension installed and enabled so I’m not sure what is causing this. Any way I can send logs or something else that would be more helpful?



image

This being said, I have reinstalled Cursor, & reinstalled this extension several times but the expected behavior is consistently missing.

So turns out I was using the Open VSX Marketplace directly, instead of Cursor Marketplace:

When I deleted this part from User Settings (JSON) it defaulted to Cursor Marketplace and the language servers started working again. Thanks!

@Noja121 – you can set the overrides in cursorpyright.analysis.diagnosticSeverityOverrides. If set the cursorpyright.analysis.typeCheckingMode to “off”, then you add rules to turn on errors for imports; if you start at “basic” you can turn off rules to remove the excessive red ink.

@Emilio_Martinez – Pylance is not supported in Cursor, unfortunately. However, the ms-python.python extension is supported (our Cursor Python extension depends on it). Could you link me to the micro python extension so I can take a look?

@kaandok – hmm, let me look into this. Custom marketplaces should be supported in 1.2. This might be a regression from when we updated the base vscode version.

@yagiz – great, glad that fixed it!

1 Like

not sure if this is related, but it seems like: 1.2.1 broke LSPs for me too

this is how a Ruby file looks like

and I can see tons of errors on the dev console

Trying to change the color theme doesn’t do anything either.

One more thing I noticed is the output of Cursor git indexing:

2025-07-04 09:47:59.053 [warning] PR indexing denied by server: This feature is still rolling out and will be available soon.
2025-07-04 09:47:59.053 [error] Error during indexing setup: This feature is still rolling out and will be available soon.
2025-07-04 09:52:57.777 [info] doUpdate: Disposing completed index job...
2025-07-04 09:52:57.777 [info] MultiBranchIndexJob dispose
2025-07-04 09:52:57.777 [info] Aborting multi-branch indexing job.
2025-07-04 09:52:57.803 [info] Doing a startup handshake for git indexing.
2025-07-04 09:52:57.986 [warning] PR indexing denied by server: This feature is still rolling out and will be available soon.
2025-07-04 09:52:57.988 [error] Error during indexing setup: This feature is still rolling out and will be available soon.

Has anyone had any luck with fixing their Cursor? Nothing seems to work for me to have proper Python syntax highlighting (either with the Anysphere extension or with basedpyright). All marketplace options are configured correctly and I’ve run fresh installs (+ wiped local files) several times with 1.0, 1.1 and 1.2.

This is incredibly frustrating and is basically rendering Cursor unusable.

No luck here. I tried opening a feedback post on it but no results.
The move to basedpyright /whatever brakes my usability to the point I’m now looking for alternatives to cursor.

1 Like

No luck here as well… Extremly frustrating

1 Like

Extremely disappointed by whoever is doing support for Cursor. Have opened a seperate issue and no one has even bothered to reply. Seems to be a fairly common issue for the most popular language. Would appreciate any help!

1 Like

Hey everyone!
For those who were having issues with basedpyright, here’s what worked for me:

I created a file called pyrightconfig.json at the root of my project and added the following config:

I came to this solution by analyzing the anysphere.cursorpyright extension.

My Cursor version:
1.2.4

Hope this helps someone! :slight_smile:

4 Likes

It works, great thanks for your help.
So, anysphere.cursorpyright isn’t working as expected, and this configuration makes the default VS Code Python extension handle type checking?

Wait.. we have both pylance (ms-python.vscode-pylance) and pyright (anysphere.pyright) installed and enabled. Sounds like we should uninstall pylance? I never took the time to realize they are overlapping extensions (?)

Should we be using ‘anysphere.pyright’ or ‘anysphere.cursorpyright’? I am guessing the ‘cursorpyright’ one… so, we need to remove pylance and the current version of pyright we are using, and then install anysphere.cursorpyright ?

OK, last question… we updated to anysphere.cursorpyright. Looks like it auto update our workspace settings to have the following:

"python.languageServer": "None",

is that correct, I could not find documentation on this.

Hi @whe, yes, the anysphere.pyright extension is the old one; I’d remove that one. You don’t need it if you are using anysphere.cursorpyright.

When using anysphere.cursorpyright, the python.languageServer setting must be “None”. We’ll set the setting at all config levels (system, user, workspace), but you can remove it from the workspace.

@user7 – setting this to “off” suppresses all errors raised by the language server that are not explicitly enabled.

2 Likes

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.