pycodestyle
pyre-check
pycodestyle | pyre-check | |
---|---|---|
7 | 24 | |
4,983 | 6,692 | |
0.4% | 0.4% | |
7.1 | 9.9 | |
22 days ago | 7 days ago | |
Python | OCaml | |
GNU General Public License v3.0 or later | MIT License |
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.
pycodestyle
-
Enhance Your Project Quality with These Top Python Libraries
PEP8 (pycodestyle): Named after Python’s PEP 8 style guide, this tool checks your Python code against some of the style conventions in PEP 8.
-
flake8-length: Flake8 plugin for a smart line length validation.
pycodestyle linter (used in Flake8 under the hood by default) already has E501 and W505 rules to validate the line length. flake8-length provides an alternative check that is smarter and more forgiving.
-
2 Static Analysis Tools to Enhance Your Productivity
[flake8] max-line-length = 88 ignore = # False positive whitespace before ':' on list slice. # See https://github.com/PyCQA/pycodestyle/issues/373 for details E203
-
Code Quality Tools in Python
Linters analyze code to detect various categories of issues like logistical issue and stylistic issues. Some popular linters are Pylint, pycodestyle, Flake8 and Pylama.
-
A simple randomic "Rock Paper Scissors"
Regarding item 4), sorry to make a relatively minor correction to your very helpful post, but you linked to a four-year-old version of a tool that has received many updates since. Here is the current version (note that the project has been renamed). In addition, it is decidedly not an official tool; making its unofficial status clear was the reason for the name change.
-
[plugin] pycodestyle.nvim
Link. When I write Python I usually have pycodestyle as my linter, and this got me thinking: If I already have a linter configuration for a project, why not just use the linter configuration as my editor configuration as well? The linter configuration is useful to others even if they use a different editor and I don't have to duplicate it in a local vimrc or editorconfig file. I can just use what I already have.
-
How to run program from everywhere (on CLI) like pycodestyle
setuptools provides an easy way to do this via entry_points. Here's the relevant part of setup.py in pycodestyle
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.
What are some alternatives?
black - The uncompromising Python code formatter
pyright - Static Type Checker for Python
Flake8 - flake8 is a python tool that glues together pycodestyle, pyflakes, mccabe, and third-party plugins to check the style and quality of some python code.
mypy - Optional static typing for Python
autopep8 - A tool that automatically formats Python code to conform to the PEP 8 style guide.
pytype - A static type analyzer for Python code
flake8-too-many - A flake8 plugin that prevents you from writing "too many" bad codes.
typeshed - Collection of library stubs for Python, with static types
pyflakes - A simple program which checks Python source files for errors
flake8
editorconfig-vim - EditorConfig plugin for Vim
typing - Python static typing home. Hosts the documentation and a user help forum.