From: Ɓukasz Langa Date: Tue, 31 Aug 2021 16:00:16 +0000 (+0200) Subject: bpo-44135: Refine explanation of how passing tuples to issubclass() behaves (GH-26193... X-Git-Tag: v3.9.8~201 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=5f66ad09ff2c51521e1512888cac84e0cc0907d4;p=thirdparty%2FPython%2Fcpython.git bpo-44135: Refine explanation of how passing tuples to issubclass() behaves (GH-26193) (GH-28094) This is a quasi-backport to 3.9 since the wording in this branch is different. Co-authored-by: Zachary Kneupper zachary.kneupper@gmail.com --- diff --git a/Doc/library/functions.rst b/Doc/library/functions.rst index c5c1c161293f..39ce338d3887 100644 --- a/Doc/library/functions.rst +++ b/Doc/library/functions.rst @@ -862,8 +862,8 @@ are always available. They are listed here in alphabetical order. Return ``True`` if *class* is a subclass (direct, indirect or :term:`virtual `) of *classinfo*. A class is considered a subclass of itself. *classinfo* may be a tuple of class - objects, in which case every entry in *classinfo* will be checked. In any other - case, a :exc:`TypeError` exception is raised. + objects, in which case return ``True`` if *class* is a subclass of any entry + in *classinfo*. In any other case, a :exc:`TypeError` exception is raised. .. function:: iter(object[, sentinel])