Explain that GenericAlias instances are not considered to be a class
#1993
+11
−0
Conversation
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
|
All commit authors signed the Contributor License Agreement. |
Member
|
I don't think this belongs in the typing spec since it's about runtime behavior. |
Collaborator
|
I agree with Jelle that this doesn't belong in the typing spec. We've intentionally avoided documenting runtime implementation details in the typing spec. |
Author
|
Got you, thanks. This part of the document(from typing docs) was "quoted" in the issue, I though that I should updated that part. Now I need to find out where I should document that behaviour in python docs. If you have any suggestions, let me know, appreciated ) |
Member
|
This could be added to https://docs.python.org/3.14/library/stdtypes.html#generic-alias-type |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
I added new explanations to the part of the document that relates to that issue (after explanation of "type erasure").
Related issue: python/cpython#132467