pycodestyle
ruff
pycodestyle | ruff | |
---|---|---|
7 | 95 | |
4,983 | 26,725 | |
0.4% | 3.9% | |
7.1 | 10.0 | |
22 days ago | about 11 hours ago | |
Python | Rust | |
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
ruff
-
Ask HN: High quality Python scripts or small libraries to learn from
I think I mention this all the time when this comes up, but I learned the most 'best practices' through using ruff.
https://docs.astral.sh/ruff/
I just installed and enabled all the rules by setting
-
Enhance Your Project Quality with These Top Python Libraries
Ruff is a Python linter that helps to identify and remove code smells. Over 700 built-in rules: Ruff includes native re-implementations of popular Flake8 plugins, like flake8-bugbear. And also built-in caching to avoid re-analyzing unchanged files.
-
Ask HN: What interesting project ideas you've got but have no time to work on?
Because the Python's "ast" modules is too slow, and lacks proper "format" feature (it has unparse but it removes comments, and forgets the current style completely). I use "ruff" a lot (https://github.com/astral-sh/ruff) which is in Rust. But I want to be able to implement fast custom linters in Go (linters that ruff / fixit lack, and Python linters lack or are too slow).
-
Rye: A Vision Continued
I think it’s interesting that rye uses ruff (https://github.com/astral-sh/ruff) for linting and formatting. That’s the right call, and it’s also correct to bundle that in for an integrated dev experience.
I had to guess, that’s the path that the Astral team would take as well - expand ruff’s capabilities so it can do everything a Python developer needs. So the vision that Armin is describing here might be achieved by ruff eventually. They’d have an advantage that they’re not a single person maintenance team, but the disadvantage of needing to show a return to their investors.
- An fast Python linter and code formatter, written in Rust
-
Smooth Packaging: Flowing from Source to PyPi with GitLab Pipelines
Adding more weight to ease of setup and configurability, the choice came down on flake8. It is easy to integrate, since its also available through pip and let’s you configure which standards you want to omit by simply stating them as a list via the --ignore switch. Moving to ruff appears quite smooth, so future updates may do so.
- Show HN: Marimo – an open-source reactive notebook for Python
-
AST-grep(sg) is a CLI tool for code structural search, lint, and rewriting
I confess I stole the pip recipe from Charlie :D
https://github.com/astral-sh/ruff/blob/main/.github/workflow...
-
Embracing Modern Python for Web Development
Ruff is an emerging tool in the Python ecosystem that describes itself as "an extremely fast Python linter and code formatter, written in Rust".
- Ruff: An fast Python linter and code formatter, written in Rust
What are some alternatives?
black - The uncompromising Python code formatter
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.
pyright - Static Type Checker for Python
flake8-too-many - A flake8 plugin that prevents you from writing "too many" bad codes.
Pylint - It's not just a linter that annoys you!
pyflakes - A simple program which checks Python source files for errors
editorconfig-vim - EditorConfig plugin for Vim
pre-commit - A framework for managing and maintaining multi-language pre-commit hooks.