Cursor’s Built-in Pyright/Pylance Shows Unwanted Type Warnings in Common Workflows

Describe the Bug

After the latest Cursor upgrade, I noticed that the Microsoft Python extension (Pylance) no longer fully integrates with the updated Cursor environment. Specifically, type checking and auto-completion have become unreliable in pandas workflows. For instance, calling .describe() on a pandas Series now triggers an incorrect warning:

Cannot access attribute "describe" for class "ndarray[Any, Unknown]"

This seems to be caused by Cursor overriding or failing to correctly propagate type inference through the new runtime environment, possibly due to how it wraps variables or renders cells.

Steps to Reproduce

I just update the cursor to this version and it starts highlighting this problem.

When I switch back to vscode, it disappears.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.4
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90
Date: 2025-07-10T16:53:59.659Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

The setup was done by the Agent, so I don’t know the details, but I think if you explicitly add the linting rules to your repo, the IDE will use those instead of its own.

Hi @jluo41 and @Artemonim, you can set the setting cursorpyright.analysis.typeCheckingMode to off to hide all errors.

Hi @ravirahman. That’s not really a solution, as it will remove all useful errors as well, e.g. on imports. This change has broken my Python workflow with Cursor, so I would appreciate a fix ASAP. I love Cursor but I am certain this will otherwise lead to significant churn for you guys, there are alternatives.

Hi @joelo, @jluo41, and @Artemonim – thank you for this report. We have fixed this in version 1.0.6 of the Anysphere Python extension to provide defaults that are more similar to Pylance / VSCode. Could you try upgrading the extension?

1 Like

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