From c0063bdc7b5fed98c6799f3da0a954a775e3d89e Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Mon, 4 Apr 2022 19:59:04 -0700 Subject: [PATCH] bpo-47007: [doc] `str` special method lookup (GH-31863) Clarify the `str()` docs to point out that `object.__str__()` follows special method lookup. Co-authored-by: Jelle Zijlstra (cherry picked from commit bb86d1d9fbd1888524e04475383f4ea764277f67) Co-authored-by: Vanshaj Singhania <8797467+itsvs@users.noreply.github.com> --- Doc/library/stdtypes.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Doc/library/stdtypes.rst b/Doc/library/stdtypes.rst index b10909d81af0..4be4d1daa831 100644 --- a/Doc/library/stdtypes.rst +++ b/Doc/library/stdtypes.rst @@ -1448,7 +1448,8 @@ multiple fragments. depends on whether *encoding* or *errors* is given, as follows. If neither *encoding* nor *errors* is given, ``str(object)`` returns - :meth:`object.__str__() `, which is the "informal" or nicely + :meth:`type(object).__str__(object) `, + which is the "informal" or nicely printable string representation of *object*. For string objects, this is the string itself. If *object* does not have a :meth:`~object.__str__` method, then :func:`str` falls back to returning -- 2.47.3