Feedback on new default rules #27213

Activity

1. ntBre

   added

   rule-selectionRelated to enabling or disabling rulesRelated to enabling or disabling rules

   trackingA "meta" issue that tracks completion of a bigger task via a list of smaller scoped issues.A "meta" issue that tracks completion of a bigger task via a list of smaller scoped issues.

   on Jul 27, 2026
2. ntBre

   added this to the v0.17 milestone on Jul 27, 2026
3. ntBre

   added sub-issues on Jul 27, 2026

   • DTZ rules should not be in the default set #27197
   • Please remove all rules without an automated fix from default rules #27177
   • SIM118 complains about .keys() even when the object isn't a dict #27224
4. ntBre

   added a sub-issue on Aug 11, 2026

   • collapsible-if rule obscures conditional structure #27647
5. meejah commented on Aug 26, 2026

   

   meejah

   on Aug 26, 2026

   More actions

   Hopefully this is the correct spot.

   I've been using ruff on a minor project, and recently made a PR for it. There are a bunch of new rules added to ruff (great!) but I don't want to fix them all right now. My two options are:

   • pin ruff to some exact version
   • figure out what rules to add to the ignore set

   Overall, I prefer to upgrade things. It would be nice if ruff had an option to spit out "ignore" config for either:

   • all currently-failing lints
   • all new default lints "from version X" or similar

   The latter feature could be something in the release-notes I suppose, like "to ignore all the new defaults this version, put ... in your config".
   (In my case this was upgrading from 0.15.7 -> 0.16.4 but the exact versions likely don't matter)

   As a workaround, the output from ruff check --statistics comes pretty close -- with a little text-manipulation it's fairly easy to add to the config.

   👍React with 👍1Reacted by RACZ Andras
6. ntBre commented on Aug 26, 2026

   

   ntBre

   on Aug 26, 2026

   ContributorAuthor

   More actions

   Thanks for the feedback!

   We've previously discussed a somewhat similar approach to this problem as "baselines" (#1149). Another current option, though it can be a bit noisy depending on how many diagnostics you have, is to use --add-noqa or --add-ignore, which will suppress all diagnostics inline instead of ignoring the rules project-wide.

   The latter feature could be something in the release-notes I suppose, like "to ignore all the new defaults this version, put ... in your config".

   You may have missed it since you were upgrading across the minor release boundary, but a variant of this was included in the 0.16.0 blog post:

   If you want to revert to the old default set, you can easily select the old rules with this configuration:

   [lint]
   select = ["E4", "E7", "E9", "F"]

   I thought that was also in the changelog, but it looks like I didn't copy it over there!

   Since I love playing with jq, you could also get the list of codes to ignore with something like:

   ❯ ruff check --no-cache --output-format=json | jq '[.[].code] | unique'
   [
     "B007",
     "E402",
     "F403",
     "F821",
     "TID251",
     "TID253"
   ]

   👍React with 👍1Reacted by RACZ Andras
7. ntBre

   added a commit that references this issue on Aug 27, 2026

   Update preview default rules and categories (#27877)

   ...

   5fdab73
8. sharkdp

   added a commit that references this issue on Aug 31, 2026

   Update preview default rules and categories (#27877)

   ...

   27fb489
9. ntBre

   modified the milestones: v0.17, v0.18 on Sep 23, 2026