gh-137191: Fix how type parameters are collected from Protocol and Generic bases with parameters#137281
Merged
sobolevn merged 3 commits intopython:mainfrom Aug 3, 2025
Merged
gh-137191: Fix how type parameters are collected from Protocol and Generic bases with parameters#137281sobolevn merged 3 commits intopython:mainfrom
Protocol and Generic bases with parameters#137281sobolevn merged 3 commits intopython:mainfrom
Conversation
…` and `Generic` bases with parameters
JelleZijlstra
approved these changes
Jul 31, 2025
Member
Author
|
Thank you! I will keep this open for a bit for any extra feedback :) |
Member
Author
|
Looks like there are no objections / suggestions. Merging! |
|
Agent-Hellboy
pushed a commit
to Agent-Hellboy/cpython
that referenced
this pull request
Aug 19, 2025
…` and `Generic` bases with parameters (python#137281)
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.
While fixing this problem, I've also noticed that code like
never produced any
TypeError, it is in contrast towhich produced this error as it should. I've fixed this as well.
TypeErrorwhen omitting aProtocoltype argument with default #137191