Do not treat match value patterns as isinstance checks
#20146
+91
−27
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.
As discovered by @randolf-scholz in #20142,
mypytreats value patterns in match statement in a completely wrong way.From PEP 622:
Existing tests for the feature are invalid: for example,
must reveal
object, and testtestMatchValuePatternNarrowsasserts the opposite. Here's a runtime example:I have updated the existing tests accordingly.
The idea is that value patterns are essentially equivalent to
if foo == SomeValuechecks, notisinstancechecks modelled byconditional_types_wit_intersection.The original implementation was introduced in #10191.