Cursor Pyright "Python" extension information

Inside the settings block, you can add this setting – e.g.

"customizations": {
  "vscode": {
    "settings": {
        "[python]": {
          "editor.formatOnSave": true,
          "editor.codeActionsOnSave": {
            "source.fixAll": "explicit",
            "source.organizeImports":"explicit"
          },
          "editor.defaultFormatter": "charliermarsh.ruff"
        },
        "python.defaultInterpreterPath": "/usr/local/bin/python3",
        "cursorpyright.analysis.typeCheckingMode": "off"
      },
    }
  }
}

Setting “cursorpyright.analysis.typeCheckingMode” to “off” is the key of this problem.

How to disable this? The cursor-pyright raises so many issues. If I cannot disable it, I will choose to refund and use another tool than cursor.

@ravirahman Hi dear ravirahman, I have probed this new Cursor-Pyright. I just would like to report some highlighting discrepancies between Cursor’s and MS’ Pyright now.

Apart from all other issues I haven’t had time to probe with, I can observe that highlighting regarding decorators and the property methods are a bit different. In MS’ version, the decorators uses the colour the same as classes, but here in Cursor’s, function highlighting is being used. Also for property methods, MS’ Pyright uses the colour the same as all variables, but here in Cursor’s, normal functions’ highlighting is being used.

For your convenience, this is the legacy performance of MS’ Pylance.

Also, I wonder if there are any plans of releasing Cursor’s Pyright into GitHub so that raising issues would be easier?

@fingertap – you can set the setting cursorpyright.analysis.typeCheckingMode to ‘off’ to disable most syntax errors, and cursorpyright.disableLanguageServices to fully disable the language server.

@borjigin-mergen – our extension is based on basedpyright. Could you raise an issue in their GitHub?

Sure, the issue has been raised there. If you need, this is the link: