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 updates
ruff
in.pre-commit-config.yaml
from 0.6.0 to 0.11.12, changes itsid
from the legacyruff
alias toruff-check
(which is better distinguished fromruff-format
, which we also have a hook for), and applies the few style changes it newly recommends throughout the code. The style changes seem to make things slightly clearer overall.This also updates some other pre-commit hooks, but those don't require any changes to the code.
Currently the
ruff
dependency inrequirements-dev.txt
doesn't specify a version, so no change is needed there. This update may be seen as bringing thepre-commit
version in line with what users will usually have locally withpip install -e ".[test]"
.The
pre-commit
hooks are how linting is currently done on CI, so this is updatingruff
for CI. That's the most significant effect of this change. (pre-commit
is run for linting on CI probably much more often than it is used locally, to manage pre-commit hooks or otherwise, in GitPython development.)This works locally and on CI, but I'll still wait for all checks to pass before merging.