flake8-length
pycodestyle
Our great sponsors
flake8-length | pycodestyle | |
---|---|---|
6 | 7 | |
22 | 4,972 | |
- | 0.4% | |
0.0 | 7.3 | |
over 1 year ago | 10 days ago | |
Python | Python | |
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.
flake8-length
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
What are some alternatives?
flakehell - Flake8 wrapper to make it nice, legacy-friendly, configurable.
black - The uncompromising Python code formatter
mccabe - McCabe complexity 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.
flake8-type-checking - Flake8 plugin for managing type-checking imports & forward references.
autopep8 - A tool that automatically formats Python code to conform to the PEP 8 style guide.
flake8-codes - CLI tool to introspect flake8 plugins and their codes
flake8-too-many - A flake8 plugin that prevents you from writing "too many" bad codes.
wemake-python-styleguide - The strictest and most opinionated python linter ever!
pyflakes - A simple program which checks Python source files for errors
editorconfig-vim - EditorConfig plugin for Vim