Static type checker for Python
Go to file
Serhii Tereshchenko 0d0e716f92
Update ci-integration.md (#5259)
When both scripts are executed in `scripts:` section, and `pyright` reports error, second script is not executed.

Best way to ensure report are always converted, is to use `after_script:` block.
2023-06-09 08:37:45 -06:00
.github Fixed style issue. 2023-06-08 23:23:47 -06:00
.vscode Push pylance changes to pyright (#5248) 2023-06-07 15:03:40 -07:00
build Fix typos discovered by codespell (#4399) 2023-01-04 06:54:43 -07:00
docs Update ci-integration.md (#5259) 2023-06-09 08:37:45 -06:00
packages Changed the behavior of the tokenizer to emit an extra zero-length line at the end of its line array if the last character in the file is a carriage return or linefeed character. This addresses https://github.com/microsoft/pyright/issues/5251. 2023-06-08 13:20:53 -06: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.313 2023-06-07 10:33:05 -06:00
LICENSE.txt Updated LICENSE and CONTRIBUTING files. 2019-03-17 22:05:33 -07:00
package-lock.json pull-pylance-with-pyright-1.1.307 (#5093) 2023-05-10 10:56:49 -07:00
package.json Push pylance changes to pyright (#5248) 2023-06-07 15:03:40 -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

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 Pyrights 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.