Avoid syntax errors in RUF036 fixes#23764
Merged
charliermarsh merged 1 commit intomainfrom Mar 6, 2026
Merged
Conversation
ntBre
reviewed
Mar 6, 2026
| --> RUF036.py:70:7 | ||
| | | ||
| 69 | # Preserve token boundaries when fixing non-annotation expressions. | ||
| 70 | print(None | (int)and 2) |
Contributor
There was a problem hiding this comment.
Huh, I'm surprised that the rule applies to cases outside of annotations. The docs make it sound like it only applies to annotations, which is what I always expected. Should we change that instead (or in addition)?
Member
Author
There was a problem hiding this comment.
This change is necessary regardless, but yeah, it should be limited to type contexts.
ntBre
approved these changes
Mar 6, 2026
|
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
2 participants
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.
Summary
Part of: #23763.