Special-case value-expression inference of special form subscriptions#16877
Merged
AlexWaygood merged 1 commit intomainfrom Mar 20, 2025
Merged
Special-case value-expression inference of special form subscriptions#16877AlexWaygood merged 1 commit intomainfrom
AlexWaygood merged 1 commit intomainfrom
Conversation
f2b6891 to
37084f0
Compare
Contributor
|
Member
Author
Here's the link to the line in question: https://github.com/psf/black/blob/dd278cb316d75868716a0478c35b1fcd600a5249/src/black/trans.py#L54
So it's good that we no longer emit this error! |
carljm
approved these changes
Mar 20, 2025
dcreager
added a commit
that referenced
this pull request
Mar 21, 2025
* main: (26 commits) Use the common `OperatorPrecedence` for the parser (#16747) [red-knot] Check subtype relation between callable types (#16804) [red-knot] Check whether two callable types are equivalent (#16698) [red-knot] Ban most `Type::Instance` types in type expressions (#16872) Special-case value-expression inference of special form subscriptions (#16877) [syntax-errors] Fix star annotation before Python 3.11 (#16878) Recognize `SyntaxError:` as an error code for ecosystem checks (#16879) [red-knot] add test cases result in false positive errors (#16856) Bump 0.11.1 (#16871) Allow discovery of venv in VIRTUAL_ENV env variable (#16853) Split git pathspecs in change determination onto separate lines (#16869) Use the correct base commit for change determination (#16857) Separate `BitXorOr` into `BitXor` and `BitOr` precedence (#16844) Server: Allow `FixAll` action in presence of version-specific syntax errors (#16848) [`refurb`] Fix starred expressions fix (`FURB161`) (#16550) [`flake8-executable`] Add pytest and uv run to help message for `shebang-missing-python` (`EXE003`) (#16855) Show more precise messages in invalid type expressions (#16850) [`flake8-executables`] Allow `uv run` in shebang line for `shebang-missing-python` (`EXE003`) (#16849) Add `--exit-non-zero-on-format` (#16009) [red-knot] Ban list literals in most contexts in type expressions (#16847) ...
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.
Summary
Currently for something like
X = typing.Tuple[str, str], we infer the value ofXasobject. That's becauseTuple(like many of the symbols in the typing module) is annotated as a_SpecialForminstance in typeshed's stubs:ruff/crates/red_knot_vendored/vendor/typeshed/stdlib/typing.pyi
Line 215 in 23382f5
and we don't understand implicit type aliases yet, and the stub for
_SpecialForm.__getitem__says it always returnsobject:ruff/crates/red_knot_vendored/vendor/typeshed/stdlib/typing.pyi
Lines 198 to 200 in 23382f5
We have existing false positives in our test suite due to this:
ruff/crates/red_knot_python_semantic/resources/mdtest/annotations/annotated.md
Lines 76 to 78 in 23382f5
and it's causing many new false positives in #16872, which tries to make our annotation-expression parsing stricter in some ways.
This PR therefore adds some small special casing for
KnownInstanceTypevariants that fallback to_SpecialForm, so that these false positives can be avoided.Test Plan
Existing mdtest altered.
Cc. @MatthewMckee4