Fix bug in constraints solver regarding ParamSpec upper bounds#12938
Uh oh!
There was an error while loading. Please reload this page.
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.
Description
Fixes#12930.
Currently, mypy erroneously emits two errors on this snippet:
This is because of a bug in
constraints.py:ParamSpecArgsandParamSpecKwargshave upper bounds following #12668 (tuple[object, ...]anddict[str, object]respectively), but the constraints solver isn't currently aware of that fact. This PR fixes that bug.Test Plan
I added a test to one of the existing test cases.