bpo-23674: Clarify ambiguities in super() docs #15564
Conversation
rhettinger
added
docs
There was a problem hiding this comment.
Thank you @rhettinger, finally you did it before me. Here are a few change suggestions.
Doc/library/functions.rst
Outdated
|
|
||
| For example, if :attr:`~class.__mro__` of *object-or-type* is | ||
| ``D -> B -> C -> A -> object`` and the value of *type* is ``B``, | ||
| then :func:`super` searches ``C -> A -> object``. | ||
|
|
||
| The :attr:`~class.__mro__` attribute of the *type* lists the method |
There was a problem hiding this comment.
| The :attr:`~class.__mro__` attribute of the *type* lists the method |
There was a problem hiding this comment.
This one should be object-or-type
|
|
||
| For example, if :attr:`~class.__mro__` of *object-or-type* is | ||
| ``D -> B -> C -> A -> object`` and the value of *type* is ``B``, | ||
| then :func:`super` searches ``C -> A -> object``. | ||
|
|
||
| The :attr:`~class.__mro__` attribute of the *type* lists the method | ||
| resolution search order used by both :func:`getattr` and :func:`super`. The |
There was a problem hiding this comment.
| resolution search order used by both :func:`getattr` and :func:`super`. The | |
| The :attr:`~class.__mro__` |
There was a problem hiding this comment.
I prefer the wording that references both getattr and super. Those two are deeply related.
|
@rhettinger: Please replace |
|
Thanks @rhettinger for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8. |
(cherry picked from commit cd81f05) Co-authored-by: Raymond Hettinger <rhettinger@users.noreply.github.com>
|
GH-15585 is a backport of this pull request to the 3.8 branch. |
|
Thanks @rhettinger for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8. |
(cherry picked from commit cd81f05) Co-authored-by: Raymond Hettinger <rhettinger@users.noreply.github.com>
|
GH-15586 is a backport of this pull request to the 3.8 branch. |
https://bugs.python.org/issue23674