Standardize on ruff for python formatting/linting via pre-commits #183
Conversation
This file contains 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
timwoj
force-pushed
the
topic/timw/unify-python-pre-commits
branch
from
88ff803 to
6b02601
Compare
timwoj
force-pushed
the
topic/timw/unify-python-pre-commits
branch
from
6b02601 to
e7940b8
Compare
timwoj
force-pushed
the
topic/timw/unify-python-pre-commits
branch
from
e7940b8 to
4551ae1
Compare
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.
This is part of a minor effort to standardize all of our python pre-commits on the same tooling, in this case ruff. It adds one minor formatting fix and fixes a few findings from the linter (some by just suppressing them).