summaryrefslogtreecommitdiffstats
path: root/Doc/tutorial
diff options
context:
space:
mode:
authorSerhiy Storchaka <storchaka@gmail.com>2023-07-29 05:48:10 (GMT)
committerGitHub <noreply@github.com>2023-07-29 05:48:10 (GMT)
commitf2d07d3289947d10b065b2bb7670c8fb6b6582f2 (patch)
tree4951b8b9118b548a868de6995c451aa33814dc1c /Doc/tutorial
parent413ba8943e2f1d896a0568eb571a041b88589440 (diff)
downloadcpython-f2d07d3289947d10b065b2bb7670c8fb6b6582f2.zip
cpython-f2d07d3289947d10b065b2bb7670c8fb6b6582f2.tar.gz
cpython-f2d07d3289947d10b065b2bb7670c8fb6b6582f2.tar.bz2
gh-101100: Sphinx warnings: pick the low hanging fruits (GH-107386)
Diffstat (limited to 'Doc/tutorial')
-rw-r--r--Doc/tutorial/errors.rst4
-rw-r--r--Doc/tutorial/interactive.rst2
2 files changed, 3 insertions, 3 deletions
diff --git a/Doc/tutorial/errors.rst b/Doc/tutorial/errors.rst
index 8a207c3..1ec5976 100644
--- a/Doc/tutorial/errors.rst
+++ b/Doc/tutorial/errors.rst
@@ -154,7 +154,7 @@ exception type.
The *except clause* may specify a variable after the exception name. The
variable is bound to the exception instance which typically has an ``args``
attribute that stores the arguments. For convenience, builtin exception
-types define :meth:`__str__` to print all the arguments without explicitly
+types define :meth:`~object.__str__` to print all the arguments without explicitly
accessing ``.args``. ::
>>> try:
@@ -174,7 +174,7 @@ accessing ``.args``. ::
x = spam
y = eggs
-The exception's :meth:`__str__` output is printed as the last part ('detail')
+The exception's :meth:`~object.__str__` output is printed as the last part ('detail')
of the message for unhandled exceptions.
:exc:`BaseException` is the common base class of all exceptions. One of its
diff --git a/Doc/tutorial/interactive.rst b/Doc/tutorial/interactive.rst
index c0eb1fe..0d3896a 100644
--- a/Doc/tutorial/interactive.rst
+++ b/Doc/tutorial/interactive.rst
@@ -23,7 +23,7 @@ Python statement names, the current local variables, and the available
module names. For dotted expressions such as ``string.a``, it will evaluate
the expression up to the final ``'.'`` and then suggest completions from
the attributes of the resulting object. Note that this may execute
-application-defined code if an object with a :meth:`__getattr__` method
+application-defined code if an object with a :meth:`~object.__getattr__` method
is part of the expression. The default configuration also saves your
history into a file named :file:`.python_history` in your user directory.
The history will be available again during the next interactive interpreter