Repository navigation
Bind type variables in ParamSpec callable aliases - #22443
Open
mengqing88 wants to merge 1 commit into
Open
mengqing88 wants to merge 1 commit into
mengqing88 wants to merge 1 commit into
Conversation
mengqing88
force-pushed
the
fix/param-spec-alias-callable
branch
from
November 11, 2026 15:43
d776ccd to
6215214
Compare
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
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 #22399
When a generic alias over Callable is instantiated with a concrete parameter list or ellipsis in its ParamSpec slot, analyze the expanded callable so free type variables bind to the returned callable instead of being reported as unbound in the enclosing scope. Ordinary aliases and alias-definition analysis retain their existing behavior.
Tests: