[3.9] bpo-45680: Clarify documentation on GenericAlias
objects (GH-29335)
#30689
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.
The documentation on
GenericAlias
objects implies at multiple points thatonly container classes can define
__class_getitem__
. This is misleading.This PR proposes a rewrite of the documentation to clarify that non-container
classes can define
__class_getitem__
, and to clarify what it means when anon-container class is parameterized.
See also: initial discussion of issues with this piece of documentation in
GH-29308, and previous BPO issue 42280.
Also improved references in glossary and typing docs. Fixed some links.
Co-Authored-By: Erlend Egeberg Aasland [email protected]
Co-Authored-By: Ken Jin [email protected]
Co-Authored-By: Alex Waygood [email protected]
(cherry picked from commit 0eae9a2)
https://bugs.python.org/issue45680