Upgrade ruff version and rules#629
Merged
AlexWaygood merged 9 commits intopython:mainfrom Jul 8, 2025
Merged
Conversation
AlexWaygood
reviewed
Jul 8, 2025
AlexWaygood
reviewed
Jul 8, 2025
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.
In relation to the pre-commit PR #628. A while ago I started a list of ruff rules that need to be ignored in the future. With the latest version of ruff (0.12) - if we add it - some of the preview rules became active in the standard set (e.g., UP045, RUF041) but shouldn't be applied to typing_extensions.
Some of the rules I've added in this PR are still in preview, I think it makes sense to add them pro-actively.
Possibly we want RUF023 (sorted slots) only on a per line ignore.