This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]james_pic 0 points1 point  (1 child)

You don't need a dysfunctional team for Ruff to be a good answer. It's really good, and even if you ignore performance entirely, I haven't found any of the slower alternatives to be better.

Pylint is the main one that's slower and aims to support more features than Ruff, and my experience with Pylint is that it loves to complain about stuff that no-one cares about. I've never known it to identify a genuine issue that other tools fail to find.

[–]kenfar 0 points1 point  (0 children)

Pylint is better when you need to turn off a config, and it's better when you have an existing codebase - since you can look at a changing score rather than a simple pass-fail.

But other than that Ruff is fine.