pyre-check
awesome-flake8-extensions
Our great sponsors
pyre-check | awesome-flake8-extensions | |
---|---|---|
24 | 4 | |
6,692 | 1,193 | |
0.7% | - | |
9.9 | 6.4 | |
about 23 hours ago | about 1 month ago | |
OCaml | ||
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pyre-check
-
Pylyzer – A fast static code analyzer and language server for Python
Did you come across pyre in your search? MIT license and pretty fast.
https://github.com/facebook/pyre-check
-
Enhance Your Project Quality with These Top Python Libraries
Pyre is a performant type-checker developed by Facebook. Pyre can analyse codebases with millions of lines of code incrementally – providing instantaneous feedback to developers as they write code.
-
A Tale of Two Kitchens - Hypermodernizing Your Python Code Base
Pyre from Meta, pyright from Microsoft and PyType from Google provide additional assistance. They can 'infer' types based on code flow and existing types within the code.
-
Ruff v0.1.0
Have you seen Pyre[0]? Not Rust, OCaml, and pretty fast. Made by a team at Meta and open sourced on GitHub. If you use python-lsp, I wrote an extension[1] to enable integration (though I haven't tested it recently, been programming in rust; it is mostly a "for me" extension).
0: https://pyre-check.org/
1: https://github.com/cricalix/python-lsp-pyre
- Should I Rust or should I Go
- Writing Python like it's Rust
-
Buck2, a large scale build tool written in Rust by Meta, is now available
Internally we use Pyre for Python type checking: https://github.com/facebook/pyre-check
- Are there any sectors that use Haskell as a main programming language?
-
It is becoming difficult for me to be productive in Python
Before type hinting, work had intense rules and linters enforcing docstrings with types. Now, type hints and automatic pyre runs take care of all the heavy lifting.
-
Ruby 3.2’s YJIT is Production-Ready
Python now has an optional type system and if you add one of them such as mypy or pyre to your CI process and you can configure GitHub to refuse the pull request until types are added you can make it somewhat strongly typed.
If you have a preexisting codebase I believe the way you can convert it is to add the types that you know on commits and eventually you will have enough types that adding the missing ones should be easy. For the missing ones Any is a good choice.
https://pyre-check.org and https://github.com/python/mypy are popular.
awesome-flake8-extensions
-
A Tale of Two Kitchens - Hypermodernizing Your Python Code Base
Ultimately we want to test our code with Flake8 and plugins to enforce a more consistent code style and to encourage best practices. When you first introduce flake8 or a new plug-in commonly you have a lot of violations that you can silence with a #noqa comment. When you first introduce a new flake8 plugin, you will likely have a lot of violations, which you silence with #noqa comments. Over time these comments will become obsolete because you fixed the. yesqa will automatically remove these unnecessary #noqa comments.
-
Python toolkits
flake8 for linting along with following plugin (list of awesome plugin can be found here, but me and my teammates have selected the below one. Have linting but don't make it too hard.) flake8-black which uses black for code formatting check. flake8-isort which uses isort for separation of import in section and formatting them alphabetically. flake8-bandit which uses bandit for security linting. flake8-bugbear for finding likely bugs and design problems in your program. flake8-bugbear - Finding likely bugs and design problems in your program. pep8-naming for checking the PEP-8 naming conventions. mccabe for Ned’s script to check McCabe complexity flake8-comprehensions for writing better list/set/dict comprehensions.
-
Write better Python - with some help!
In addition to this out of the box -linting, there are loads of flake8 extensions that can help you with for example switching from .format() to using f-strings or checking that your naming follows the PEP8 guidelines. For example, adding flake8-length adds line length checking to the linting.
-
Standards to be aware of
And if you're using flake8, make sure to check out its plugins. Here's a good list: https://github.com/DmytroLitvinov/awesome-flake8-extensions
What are some alternatives?
pyright - Static Type Checker for Python
black - The uncompromising Python code formatter
mypy - Optional static typing for Python
Airflow - Apache Airflow - A platform to programmatically author, schedule, and monitor workflows
pytype - A static type analyzer for Python code
unimport - :rocket: The ultimate linter and formatter for removing unused import statements in your code. [Moved to: https://github.com/hakancelikdev/unimport]
typeshed - Collection of library stubs for Python, with static types
pep8-naming - Naming Convention checker for Python
flake8
flakes - list of flake8 plugins and their codes
typing - Python static typing home. Hosts the documentation and a user help forum.
portray - Your Project with Great Documentation.