Fix Any
inference when unpacking iterators that don't directly inherit from typing.Iterator
#14821
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 #14819.
Mypy currently silently infers an
Any
type when unpacking an iterator that doesn't explicitly inherit fromtyping.Iterator
(i.e., an iterator that's a structural subtype oftyping.Iterator
, but not a nominal subtype):However, we have enough information here to infer that the type of
a
should really beint
. This PR fixes that bug.There's discussion on the issue thread about an alternative solution that would involve changing some mypy behaviour that's been established for around 10 years. For now, I haven't gone for that solution.