microsoft/pyright
1
1
Fork 0
mirror of https://github.com/microsoft/pyright.git synced 2024-07-02 10:06:21 +03:00
Code Issues Projects Releases Wiki Activity
Static type checker for Python
7,567 Commits 6 Branches 450 Tags 99 MiB
Python 55.7%
TypeScript 28.3%
JSON-with-Comments 15.9%
main
Go to file
Eric Traut 2947be68bf Did more code cleanup in the assignment statement evaluation code path.
2024-07-01 20:50:20 -07:00
.github Added additional paralellization for mypy_primer (from 2 to 8 shards) to reduce feedback time on PRs. 2024-06-30 16:01:36 -07:00
.vscode Debugging (#7332) 2024-02-25 15:26:06 -07:00
build add an azure devops build (#8200) 2024-06-25 11:39:05 -07:00
docs fix broken markdown link (#8186) 2024-06-20 15:55:37 +02:00
packages Did more code cleanup in the assignment statement evaluation code path. 2024-07-01 20:50:20 -07:00
.eslintignore Mass reformat ts/js/md with ESLint quick fixes and prettier (#113) 2020-02-24 16:52:23 -08:00
.eslintrc.json Added new eslint rule to enforce that protected class variables and methods should never start with an underscore. We were somewhat inconsistent here. Fixed up the code to honor this rule. 2023-04-26 16:09:58 -07:00
.gitattributes Convert repo into a lerna monorepo, add a validation workflow (#978) 2020-08-28 19:46:48 -07:00
.gitignore Create test for virtual environment (#6007) 2023-09-25 10:21:21 -07:00
.prettierignore Convert repo into a lerna monorepo, add a validation workflow (#978) 2020-08-28 19:46:48 -07:00
.prettierrc Upgrade to Prettier 2.0, reformat (#610) 2020-04-07 17:18:22 -07:00
CONTRIBUTING.md Updated "contributing" text to recommend that an enhancement request be filed prior to submitting a PR. 2022-03-29 15:51:59 -06:00
lerna.json Published 1.1.369 2024-06-25 18:02:18 +02:00
LICENSE.txt Updated LICENSE and CONTRIBUTING files. 2019-03-17 22:05:33 -07:00
package-lock.json Bump braces from 3.0.2 to 3.0.3 (#8204) 2024-06-22 15:24:27 +02:00
package.json Push pylance changes to pyright (#7719) 2024-04-17 11:46:31 -07:00
README.md Added link to pyright playground in main README. 2023-10-25 20:13:34 -07:00
SECURITY.md Microsoft mandatory file (#3477) 2022-05-18 15:28:38 -07:00
tsconfig.json Change all file paths to use a new URI class. (#6519) 2023-12-07 09:15:39 -08:00

README.md

Pyright

Static Type Checker for Python

Pyright is a full-featured, standards-based static type checker for Python. It is designed for high performance and can be used with large Python source bases.

Pyright includes both a command-line tool and an extension for Visual Studio Code.

Pyright Playground

Try Pyright in your browser using the Pyright Playground.

Documentation

Refer to the documentation for installation, configuration, and usage details.

Community

Do you have questions about Pyright or Python type annotations in general? Post your questions in the discussion section.

If you would like to report a bug or request an enhancement, file a new issue in either the pyright or pylance-release issue tracker. In general, core type checking functionality is associated with Pyright while language service functionality is associated with Pylance, but the same contributors monitor both repos. For best results, provide the information requested in the issue template.

Contributing

This project welcomes contributions and suggestions. For feature and complex bug fix contributions, it is recommended that you first discuss the proposed change with Pyright’s maintainers before submitting the pull request. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.