summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAndre Delfino <adelfino@gmail.com>2021-04-29 01:12:15 (GMT)
committerGitHub <noreply@github.com>2021-04-29 01:12:15 (GMT)
commit69a733bda34d413d3ad545ef3132240e5d2a7c0c (patch)
tree2a764473df3758ebd75da12a09b5a58cac339574
parent08a4803863856db47a1dde830e56f83e5c6811a2 (diff)
downloadcpython-69a733bda34d413d3ad545ef3132240e5d2a7c0c.zip
cpython-69a733bda34d413d3ad545ef3132240e5d2a7c0c.tar.gz
cpython-69a733bda34d413d3ad545ef3132240e5d2a7c0c.tar.bz2
[doc] Be more clear on super() regarding multiple base classes methods (GH-21789)
-rw-r--r--Doc/library/functions.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/library/functions.rst b/Doc/library/functions.rst
index 72441f0..7d8a669 100644
--- a/Doc/library/functions.rst
+++ b/Doc/library/functions.rst
@@ -1711,7 +1711,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).