Update Python code style guidelines regarding usage of ruff
#9209
+20
−16
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
AThousandShips
added
area:contributing
|
Marking as a draft until the main PR is merged, if it is |
Repiteo
removed
the
waiting on PR merge
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.
blackformatter withruffgodot#90457.blackformatter (which is being replaced by the PR mentioned above) withruff.contributing/development/code_style_guidelines.rstfile seems to be out of date regarding removal of hand-written pre-commit hooks introduced by Replace hand-written pre-commit hooks withpre-commitPython tool godot#88866 - I borrowed a few relevant changes from Add new documentation about the pre-commit hook #9094 in the hopes that future merge conflicts aren't too painful.