Fix TypedDict tuple context for Collection#21541
Draft
oppnc wants to merge 1 commit into
Draft
Conversation
Contributor
|
According to mypy_primer, this change doesn't affect type check results on a corpus of open source code. ✅ |
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
1 participant
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.
Fixes #8921.
Tuple expressions are contextually typed for
SequenceandIterable, but not forCollection. This meant a tuple literal containing aTypedDictliteral could fail when the expected type wasCollection[Item], even though the same expression worked for related protocols.This change adds
typing.Collectionto the tuple-like contextual typing set and adds regression coverage for bothtyping.Collectionandcollections.abc.Collection.Validation:
python -m pytest -n0 -q mypy/test/testcheck.py::TypeCheckSuite::check-typeddict.test