[pre-commit] Activate ruff checks and fix existing issues#11912
Merged
Pierre-Sassoulas merged 4 commits intoFeb 2, 2024
Conversation
bluetech
approved these changes
Feb 2, 2024
bluetech
left a comment
Member
There was a problem hiding this comment.
Nice!
👍 on bugbear (at least most of the rules).
flake8-pyi also looks very nice.
Member
Probably because |
Member
Author
|
Always thought that format called |
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
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.
Follow-up to #11901, there's some nice fixes here I think, especially automated removal of useless noqa. I would consider adding flake8-bugbear next but let me know what you think. I suppose most of the
f"{x!s}"are the default behavior in a f-string and we could replace them withf"{x}"but I'm not sure why this is not what ruff does when autofixing already.