ruff 0.16.1 check --fix (what ruff considers safe fixes) - #448
Open
gkreitz wants to merge 2 commits into
Open
Conversation
Contributor
Author
|
... and of course we run into a corner case. We had a class with a field named |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ruff 0.16 enabled a ton of new checks by default. We probably want to move to 0.16, but that will be a bit of a pain.
This PR is a first step in that direction by simply running
ruff check . --fixwith 0.16.1, applying what ruff considers to be safe fixes (and in my experience, those are indeed safe).