[ty] Omit the binding context from the display of a ParamSpec when the ParamSpec is included in the displayed type parameters of the enclosing signature#23211
Merged
AlexWaygood merged 1 commit intomainfrom Feb 10, 2026
Conversation
…the `ParamSpec` is included in the displayed type parameters of the enclosing signature
Typing conformance resultsNo changes detected ✅ |
|
Memory usage reportSummary
Significant changesClick to expand detailed breakdownprefect
|
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.
Summary
In #22435, we changed our display of
Callabletypes so that we used PEP-695 type parameters more consistently to indicate the scoping of typevars inside theseCallabletypes. As part of that change, we started omitting the binding context from the display of a type variable in aCallablesignature if the type variable was anyway being displayed as part of a type parameter list, since the appearance of the type variable in a type parameter list makes the scoping of the type variable explicit and means that the binding context just adds unnecessary noise.However, we forgot to make the same changes to
ParamSpecs: currently onmain, we always display the binding context when displaying aParamSpec. That leads to internally inconsistent displays likeThis PR updates our logic for displaying
ParamSpecs so that the binding context is also omitted from the display when theParamSpecis listed in a type parameter list for an active scope:Test Plan
mdtests updated