From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Sat, 11 Dec 2021 00:01:35 +0000 (-0800) Subject: [doc] Clarify MRO precedence in descriptor super binding section (GH-29539) (GH-29670) X-Git-Tag: v3.9.10~70 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=81a38293f2b2495bbb3b176c2912f5b6b5d3198d;p=thirdparty%2FPython%2Fcpython.git [doc] Clarify MRO precedence in descriptor super binding section (GH-29539) (GH-29670) 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 --- diff --git a/Doc/reference/datamodel.rst b/Doc/reference/datamodel.rst index 986a36cd804d..a34ec45bf4ad 100644 --- a/Doc/reference/datamodel.rst +++ b/Doc/reference/datamodel.rst @@ -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