Removed ambiguity in __init_subclass__ docs #31540
Conversation
|
@JelleZijlstra This is ready for merge. |
There was a problem hiding this comment.
Another small docs improvement I'd like to merge (cc @gvanrossum).
There is actually a more precise description of what __init_subclass__ does on line 1982-3 below. The proposed change here is more informal and I think it improves clarity.
JelleZijlstra
added
needs backport to 3.9
|
Thanks @davidgilbertson for the PR, and @JelleZijlstra for merging it 🌮🎉.. I'm working now to backport this PR to: 3.9. |
|
Thanks @davidgilbertson for the PR, and @JelleZijlstra for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10. |
|
GH-31748 is a backport of this pull request to the 3.10 branch. |
|
GH-31749 is a backport of this pull request to the 3.9 branch. |
(cherry picked from commit ab01497) Co-authored-by: David Gilbertson <[email protected]>
(cherry picked from commit ab01497) Co-authored-by: David Gilbertson <[email protected]>
|
I'm glad @miss-islington listens to backport labels even after a merge :) |
She's very smart. |
(cherry picked from commit ab01497) Co-authored-by: David Gilbertson <[email protected]>
(cherry picked from commit ab01497) Co-authored-by: David Gilbertson <[email protected]>
(cherry picked from commit ab01497) Co-authored-by: David Gilbertson <[email protected]>
Reading this for the first time, not knowing what the method does, I couldn't work out which class "that class" referred to (obviously it becomes clear once you know what the method does).