From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Thu, 29 Apr 2021 01:13:20 +0000 (-0700) Subject: [doc] Be more clear on super() regarding multiple base classes methods (GH-21789... X-Git-Tag: v3.8.10~12 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=e01003130a2bf05efc0eccc1eebd21982a63aab1;p=thirdparty%2FPython%2Fcpython.git [doc] Be more clear on super() regarding multiple base classes methods (GH-21789) (GH-25707) (cherry picked from commit 69a733bda34d413d3ad545ef3132240e5d2a7c0c) Co-authored-by: Andre Delfino Co-authored-by: Andre Delfino --- diff --git a/Doc/library/functions.rst b/Doc/library/functions.rst index 00d40d651952..036dca565783 100644 --- a/Doc/library/functions.rst +++ b/Doc/library/functions.rst @@ -1627,7 +1627,7 @@ are always available. They are listed here in alphabetical order. not found in statically compiled languages or languages that only support single inheritance. This makes it possible to implement "diamond diagrams" where multiple base classes implement the same method. Good design dictates - that this method have the same calling signature in every case (because the + that such implementations have the same calling signature in every case (because the order of calls is determined at runtime, because that order adapts to changes in the class hierarchy, and because that order can include sibling classes that are unknown prior to runtime).