PEP 257 VS Pyright

Check out https://github.com/pycqa/pydocstyle. There's a flake8 extension for it too https://pypi.org/project/flake8-docstrings/. Source: over 2 years ago

Static Type Checking with PyRight: Improve code quality and reduce bugs with PyRight, a static type checking feature not available in R. This proactive error detection ensures your applications are reliable, before you even start them. - Source: dev.to / 11 days ago

Pyright is a fast type checker meant for large Python source bases. It can run in a “watch” mode and performs fast incremental updates when files are modified. - Source: dev.to / 2 months ago

You can use pyright instead[0]. It is the FOSS version of pyright, but having some features missing. [0]: https://github.com/microsoft/pyright. - Source: Hacker News / 9 months ago

This is not the case! After reading the LSP help pages (:help lsp), I installed and configured two language servers: Typescript Language Server for JavaScript and Pyright for Python. Neovim has fantastic defaults, so things like tags, omnicompletion, and semantic highlighting (New in 0.9) are enabled and configured by default as long as your language server supports them. You can see my configuration below. Source: about 1 year ago

I've had lots of success using pyright [1] for Python projects, it has sensible defaults and can be configured with a pyproject.toml file so everyone's using the same settings. I use the Pylance VSCode extension to catch errors earlier, but I also put it in pre-commit and as a CI check, so all contributors are committing the same quality of typed code. With more complex types, I've found it isn't necessary to do... - Source: Hacker News / about 1 year ago