]> git.ipfire.org Git - thirdparty/Python/cpython.git/commitdiff
[doc] Clarify MRO precedence in descriptor super binding section (GH-29539) (GH-29670)
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Sat, 11 Dec 2021 00:01:35 +0000 (16:01 -0800)
committerGitHub <noreply@github.com>
Sat, 11 Dec 2021 00:01:35 +0000 (01:01 +0100)
A similar sentence is present in the 'Invocation from super' section of
the descriptor HOWTO, where it is already correct.
(cherry picked from commit ee49484c0f0d0d79e8fc40835da10b78f89ae503)

Co-authored-by: Jouke Witteveen <j.witteveen@gmail.com>
Doc/reference/datamodel.rst

index 986a36cd804ddff4be5fcb7aa0773b0f21c13276..a34ec45bf4adcced127ec04247293883e9ca85f7 100644 (file)
@@ -1776,7 +1776,7 @@ Class Binding
 Super Binding
    If ``a`` is an instance of :class:`super`, then the binding ``super(B, obj).m()``
    searches ``obj.__class__.__mro__`` for the base class ``A``
-   immediately preceding ``B`` and then invokes the descriptor with the call:
+   immediately following ``B`` and then invokes the descriptor with the call:
    ``A.__dict__['m'].__get__(obj, obj.__class__)``.
 
 For instance bindings, the precedence of descriptor invocation depends on