The move to basedpyright or whatever cursor fork of it, seems like a “path to hell is paved with good intentions” .
This is a diversion from main vscode where setting a formatter, linter,type checker, debugger etc is customizable. The import setting feature might support a move from pylance but it is inherently a broken method.
I can’t figure out how to completely disable cursorpyright on a remote, let alone how to switch to other formatters.
Please drop this asap. Changing the settings.json files doesn’t help, even after window reload. deleting and disabling the extension doesn’t help and it seems like a circular import for any other vscode extension that has ms.python extension as dependency - why would you do that? hard code a redirect like that?
that is such a bad practice…
PLEASE revert. This has made cursor unusable.
You can set the setting cursorpyright.disableLanguageServices to true to effectively disable Anysphere Python while still installing the MS Python extension. We do this circular reference as the Python extension doesn’t have any LSP support by itself (VSCode does a similar thing with Pylance).
you could have brought an LSP via making a new extension pack. I couldn’t install the base ms.python extension even when setting any cursorpyright value I could find. It also get’s re-enabled and re-installed after removing other formatters.
Please drop this feature. vscode prompts a ‘check the python extension’ if no lsp. This move has made cursor unusable.
@neri1 Pylance doesn’t work out of the box.
Look into the hacks mentioned in the GitHub issue of the VSCodium project.
Use the upstream Python .vsix extension from the Microsoft Marketplace; it won’t recommend any Pyright/CursorPyright.
Watch out for maxVersion in Cursor’s product.json as it severely limits the version and will silently fail .vsix installation via drag-and-drop (unless updated).
You are still left with visual artifacts (Cursor is aliasing Pylance to their Pyright build on the extension gallery).
It’s frustrating and not straightforward, but some have succeeded in making latest release of Pylance to work under latest Cursor, including under devcontainers.