I used to see this in VSCode, and it was fixed in some specific Pyright version - it seems Cursor’s isn’t there yet?
What’s the status of this fix? This is the exact same bug that hit VSCode a couple of months ago and was resolved with an update to either the Pylance or Python extension, I can’t remember which. All of my intellisense type names are coming through as FixtureFunction[SimpleFixtureFunction@FixtureFunction… instead of the actual type names.
I’m having the same issue.
Pylance v2024.8.1
Python v2024.12.3
I have to manually installer latest pylance extension from Pylance - Visual Studio Marketplace to fix this issue.
Were you able to solve it? I can only see Pylance 2024.8.1, since Cursor seems to be based on an older version of VSCode
No, nothing yet 
Hey, a new version with an updated VSCode core will be released very soon, and you’ll be able to install the latest version of this extension.
1 Like
Thank you!
I’m now running
Version: 0.45.7
VSCode Version: 1.96.2
OS: Darwin arm64 24.2.0
But the pylance extension still says:
Identifier
ms-python.vscode-pylance
Version
2024.8.1
Last Updated
2025-01-30, 14:36:28
Do I need to do something to trigger an update from the marketplace? I’ve already restarted cursor, reinstalled python+pylance, but the version is still stuck at 2024.8.1
Hey, we have a fixed version of PyLance, as newer versions have code inside that stops the extension running on Cursor!
We hope to have a better solution around this in the future, but for now, we’re limited by the license of the original PyLance extension 
Thanks for the additional context! Where do we obtain this fixed version?
Hey, to be clear, what I mean by “fixed version” is that we lock the version of PyLance, so it cannot be updated to a higher version that will not work in VSCode, there is no “fix” that we have applied to Pylance within Cursor.
I wanted to ask about plans for addressing the extension versioning issues in Cursor. Currently, the Python debugger, Python, and Pylance extensions are all running builds that are at least 6 months old. While multiple bugs related to this have been reported on GitHub issues and forums, there hasn’t been a clear path to resolution. This isn’t a minor concern, as we’re already seeing Python testing inconsistencies, and more issues are likely to emerge over time.
This deserves more visibility (many users aren’t aware of the situation), and I’d appreciate if the Cursor team could clarify:
- Are there plans to address this? If so, what solutions are being considered?
- What’s the estimated timeline for implementation?
I respect Cursor’s vision and the team’s work, and I want to continue using the platform. To be clear - I’m not pushing for immediate fixes, but rather seeking transparency about whether these issues are being tracked and if there’s a concrete plan to address them. I mention this because I’ve often seen bug reports misinterpreted as demands for immediate fixes, leading to avoided responses.
Even without definitive decisions, keeping the community informed about the situation and updating us on future plans would be the right approach. I believe most users would be patient with solutions if kept in the loop about progress.
2 Likes
That’s unfortunate. Guess I’ll just switch to something that goes off of codium so I can actually read python typedefs from libraries that like to use dict instead of dict[str, Any]
@danperks Hey, I’m not too sure what’s the issue stopping pylance from working properly on Cursor, but I ended up doing this:
- disable extension auto-update in Cursor
- close Cursor entirely
- download
ms-python.python-2024.20.0@{your architecture}.vsixandms-python.vscode-pylance-2024.11.3.vsix(Download VS Code extensions as VSIX · GitHub) - extract them with Keka, or change it to
.zipand unzip it - go inside the
extensionfolder of each extracted vsix folder - edit the version in
packages.json, and change it to2024.12.3and2024.8.1 - go to
.cursor/extensions/, locate the installed folder of yourpythonandpylanceextension - delete everything inside except
.vsixmanifest - copy everything from
extensionfolder to the installed folder - start Cursor, if it needs you to reload the window, then reload it
This is obviously a hack, but at least it works for me now.
3 Likes
