microsoft/pyright
1
1
Fork 0
mirror of https://github.com/microsoft/pyright.git synced 2024-11-03 21:30:08 +03:00
Code Issues Projects Releases Wiki Activity
Static type checker for Python
6,362 Commits 4 Branches 468 Tags 93 MiB
Python 56.7%
TypeScript 28.8%
JSON-with-Comments 14.4%
7924640f95
Go to file
Eric Traut 7924640f95 Refactored logic to break up the validateCallArguments function in the type evaluator. It was getting very unwieldy. No functional change.
2023-07-17 14:55:49 -07:00
.github Changed mypy_primer PR script to use 2 shards (parallel action executions) rather than 1 to reduce wait times. 2023-06-14 17:36:01 -07:00
.vscode Push pylance changes to pyright (#5248) 2023-06-07 15:03:40 -07:00
build [PylanceBot] Pull Pylance with Pyright 1.1.317 (#5505) 2023-07-14 14:26:45 -07:00
docs Removed the requirement that a TypedDict be marked @final for it to be considered for type narrowing as part of a S in D type guard pattern. This requirement wasn't sound because TypedDict is a structural type (i.e. a protocol), so @final doesn't have any real meaning. 2023-07-17 08:01:52 -07:00
packages Refactored logic to break up the validateCallArguments function in the type evaluator. It was getting very unwieldy. No functional change. 2023-07-17 14:55:49 -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 document highlight fixes, dict completions improvements for non string literals (#2084) 2021-07-14 13:14:42 -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.317 2023-07-12 14:33:46 +02:00
LICENSE.txt Updated LICENSE and CONTRIBUTING files. 2019-03-17 22:05:33 -07:00
package-lock.json [PylanceBot] Pull Pylance with Pyright 1.1.317 (#5505) 2023-07-14 14:26:45 -07:00
package.json [PylanceBot] Pull Pylance with Pyright 1.1.317 (#5505) 2023-07-14 14:26:45 -07:00
README.md Fixed broken links in README for npmjs page. Added missing link to command line interface documentation in sidebar. 2023-03-09 09:46:17 -07:00
SECURITY.md Microsoft mandatory file (#3477) 2022-05-18 15:28:38 -07:00
tsconfig.json Enabled "noImplicitOverride" compiler flag and added missing "override" keywords. 2021-06-15 17:27:16 -07: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.

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.