4 ms·
Yeah Ruff and Pylint can be used in a complementary way. Pylint implements rules that Ruff does not, and vice versa. I think Ruff might actually support more _t
by charliermarsh 4y ago
Yeah Ruff and Pylint can be used in a complementary way. Pylint implements rules that Ruff does not, and vice versa. I think Ruff might actually support more _total_ rules than Pylint at this point (not a great metric), but Pylint does more cross-file analysis and type inference. [1]
Some teams use Ruff alongside Pylint, some have replaced Pylint with Ruff entirely (Dagster is a good example [2]), especially those already using a type checker alongside their linter.
[1] https://beta.ruff.rs/docs/faq/#how-does-ruff-compare-to-pylint https://beta.ruff.rs/docs/faq/#how-does-ruff-compare-to-pyli...
[2] https://twitter.com/schrockn/status/1612615862904827904 https://twitter.com/schrockn/status/1612615862904827904
- epage 4y agoWhen you are already using flake8/ruff and mypy, there is little room left for pylint in my opinion. It might have some extra checks but they aren't enough to justify the performance hit.
- charliermarsh 4y agoBy the way: epage, you are a hero. I am very grateful for everything you build.
- munch117 4y agoI use a script that identifies modified files in my working copies, runs pyflakes on them, and after that pylint -E. By the time pylint finishes, I'll have already fixed most of the low-hanging fruit that pyflakes found, and then I look through the pylint messages to see if there's anything additional. There's very little waiting for pylint that way.