You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I currently use Pylint for my projects and would love to switch to Ruff. I understand not all Pylint rules are implemented yet, but my question is if it's possible to select all rules that are already implemented? Running ruff check --select PL will select the rules that are specific to Pylint, but it doesn't include all the other rules that are already covered by another tool (e.g. N805 which matches Pylint's E0213).
Is there currently a way to select all of the rules that match with Pylint? Or would it be possible to implement a way to select these, in order to provide a smoother migration path for users of other tools?
The text was updated successfully, but these errors were encountered:
Is there currently a way to select all of the rules that match with Pylint?
I'm sorry. There's currently no such way. We could consider adding aliases for these rules but I'd have to double check if aliases work when selecting a linter-group instead of a specific rule.
Our long-term goal is to recategorize our rules and to make the upstream linter groups less prominent (or remove them entirely). Instead, we want to focus on giving users an easy way to opt in to the rules relevant for their project. See #1774
I currently use Pylint for my projects and would love to switch to Ruff. I understand not all Pylint rules are implemented yet, but my question is if it's possible to select all rules that are already implemented? Running
ruff check --select PL
will select the rules that are specific to Pylint, but it doesn't include all the other rules that are already covered by another tool (e.g. N805 which matches Pylint's E0213).Is there currently a way to select all of the rules that match with Pylint? Or would it be possible to implement a way to select these, in order to provide a smoother migration path for users of other tools?
The text was updated successfully, but these errors were encountered: