-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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.
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
[pyupgrade
] Show violations without auto-fix for UP031
#11229
Conversation
|
code | total | + violation | - violation | + fix | - fix |
---|---|---|---|---|---|
UP031 | 134 | 134 | 0 | 0 | 0 |
cc340aa
to
a26ab72
Compare
I reverted the change to the diagnostic message because it floods the ecosystem changes, making it difficult to see the results related to unconditionally emitting the diagnostic. |
The changes look reasonable to me but I would like a second opinion, especially if we should gate this behind preview first. @AlexWaygood wdyt? |
This seems reasonable to me too. For a stylistic/modernisation rule like this, it can be annoying if it has lots of complaints that can't be autofixed. However, the unfixable complaints here are relatively small in number: most complaints from this rule are still autofixed. I'd also prefer if this was a preview-only change first, though, just to be on the safe side. |
Summary
This shows violations of the
UP031
rule which can't be auto-fixed, so that they can be fixed manually (similar to the pylintconsider-using-f-strings
rule)Test Plan
Updated fixtures.