Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc(FAQ): More precise PyLint comparision #10756

Merged
merged 2 commits into from
Apr 5, 2024
Merged

doc(FAQ): More precise PyLint comparision #10756

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e124bc6
doc(FAQ): More precise PyLint comparision
buhtz Apr 3, 2024
7e5631f
Tweaks
charliermarsh Apr 5, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion docs/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,7 +127,13 @@ those using Ruff alongside a [type checker](faq.md#how-does-ruff-compare-to-mypy
which can cover some of the functionality that Pylint provides.

Like Flake8, Pylint supports plugins (called "checkers"), while Ruff implements all rules natively.
Unlike Pylint, Ruff is capable of automatically fixing its own lint violations.
Therefore, the rule group `PY` also includes some of those rules that when using Pylint need to be
explicitly activated through plugins. Unlike Pylint, Ruff is capable of automatically fixing its own
lint violations.

Another difference is that Ruff uses a slightly different definition when it comes to counting
branches in code. Ruff does count try blocks themselves as branches and therefore will warn earlier
about [`too-many-branches`](rules/too-many-branches.md) (`PLR0912`).

Pylint parity is being tracked in [#970](https://github.com/astral-sh/ruff/issues/970).

Expand Down
Loading