-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Type Stub PEP #20
Comments
Hi Sebastian, thanks for your interest. Keep in mind that pyright is a work in progress. It's a side project with no full-time engineering team behind it. In that respect, I don't know if it has yet to earn a spot on this list. There is one entry that I would like to encourage you to add. Microsoft does have an officially-supported Python Language Server, an extension for VS Code that has been downloaded over 35M times already. It contains a Python type checker and is fully supported by a team at Microsoft. They are making improvements to it all the time. It isn't currently offered in the form of a command-line tool, but it is a capable type checker and deserves to be included in your list. You can contact the maintainers through the GitHub site I referenced above. |
Thank you for your pointer to the language server. If at some point in the future you feel that pyright should be added to the list, please let us know, either in our current repository, or in the PEPs respository after the PEP is released. |
Together with @rchen152, @Solumin, and @JelleZijlstra I am currently writing a PEP about type stubs. (Progress is currently stalled a bit, since other projects took precedence, but I plan to continue working on it soon.) The PEP includes a reference section with links to existing type checkers and I'd like to include pyright. Could you give a brief, one-line explanation to be included in the PEP about what makes pyright special, compared to the other type checkers?
For reference, here are the existing explanations:
Edit: https://github.com/srittau/type-stub-pep
The text was updated successfully, but these errors were encountered: