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 <jelle.zijlstra@gmail.com>
(cherry picked from commit bb86d1d9fbd1888524e04475383f4ea764277f67)

Co-authored-by: Vanshaj Singhania <8797467+itsvs@users.noreply.github.com>

diff --git a/Doc/library/stdtypes.rst b/Doc/library/stdtypes.rst
index b330335773103bf0ce3f23aada2d326eed220d8a..28082b42d7923b3412d8f6f3371724b2e2022e84 100644 (file)
--- a/Doc/library/stdtypes.rst
+++ b/Doc/library/stdtypes.rst
@@ -1479,7 +1479,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__() <object.__str__>`, which is the "informal" or nicely
+   :meth:`type(object).__str__(object) <object.__str__>`,
+   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