Surprising mandatory pylance uninstall

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After the latest update I see a warning: “In order to use Anysphere Python, ms-python.vscode-pylance must be uninstalled.” and pylance not working.
Do I really have to disable the standard extensions installed to make cursor work? This just doesn’t seem right that one day after update I have to re-manage my extensions

Steps to Reproduce

Have the app with standard pylance installed and update to the latest version

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.5.11
VSCode Version: 1.99.3
Commit: 2f2737de9aa376933d975ae30290447c910fdf40
Date: 2025-09-05T03:48:32.332Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

26 Likes

I’ve just had this pop up as well. It wants me to uninstall and restart cursor. But I’m concerned what the repercussions might be for the program I have in development. Can i safely ignore this?

Same here. Is pylance completely banned now in Cursor? What are the alternatives?

2 Likes

Following, just had this popup as well.

Seeing this as well this morning on Windows 11

I’ve been getting the same message for the last couple days. I’ve simply ignored the message (for now) and have seen no issues.

2 Likes

Same here, and also think this is kind of shady. Has there been any communication from Cursor about this? Is this intended?

As @chrisenstrom mentioned, ignoring the message works, but development becomes a pain since there is no typehints without pylance enabled.

1 Like

I have the same issue as of today.

same

We’re on this - apologies. Fix coming in next hour (no reinstall needed).

3 Likes

Good, I was in a middle of working of tests and suddenly the entire ide stopped working as expected.

I don’t know who this is relates to but it sounds to me like it’s related to here. so i am attaching this video of a bug.

What are we seeing in the video?

  1. Normal cursor usage, I have been working on python tests using pytest and fixtures of a while now and you could have always jumped to the definition reference by ctrl+click the fixture name on the test, demonstrated working
  2. after window reload it stops working and shows in-file references mostly
  3. after disabling the python extension, reloading (important) and enabling it again the ctrl+click and colors return to normal operation
    https://drive.google.com/file/d/1dJtprhRlZedI8n_mo21JgfHcKFJApEBS/view?usp=sharing

Pressed confirm, why did I believe it… Cannot find pylance in extensions marketplace anymore

2 Likes

Hi all,

There was a glitch on our backend that caused our Python language server to be distributed automatically. It is not required that you upgrade; you can uninstall our Python extension in the settings:

7 Likes

well, cursor just broke my config lol
honestly, I’m dropping Cursor, Claude Code or Codex CLI at least do not break my Text Editor

It ended up removing Pylance from my installation, so great now no more static typing there. Reply from their team say to uninstall their Python language server. I did it, ok fine.

Guess what, now impossible to install Pylance back again.

5 Likes

Uninstalling the cursor’s python extension although resolved the issue of ctrl+click fixture reference not working now cannot reference any other function and class.

1 Like

Just had an issue with missing language server reported by the Python extension. I have Pylance installed, and going to VSCode Settings > Extensions > Python > Language Server then selecting Pylance worked for me, restoring the missing functionality. For some reason I wasn’t able to go there via quick commands as they were reported as “not registered”, in that case open the settings page manually.

1 Like

Same here, unable to install pylance back anymore, infact can’t even find it. This is so stupid

2 Likes

Has anyone found a way to continue using Python with Cursor… for the past 2 (maybe 3) since this pylance thing popped up, I can’t get all files from being read, and an astronomical amount of problems on my running code… I have tried settings for basedpyright, other extensions… nothing is getting me back to a place close to where I was 2-3 days ago…
has anyone found any settings or extensions that approximate the normal of 2-3 days ago before this happened?

1 Like

nah, went back to vscode for the moment, its still not fixed

1 Like