ENH: Refactor the typing "reveal" tests using typing.assert_type
#24635
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.
Closes #21505
Python 3.11 will add the new
typing.assert_type
function, which is used for validating that two types are equivalent while static type checking. Switching from the type-comments, currently used for validating the revealed type, totyping.assert_type
has a number advantages:typing.assert_type
is agnostic w.r.t. the particular type checkers, so this means we could in principle easily run the tests with other type checkers besides mypy with fairly minimal changes to the relevant test functions.Probably want to merge after #24634 and #24587 to minimize merge conflicts.
Examples