summaryrefslogtreecommitdiffstats
path: root/Doc/tutorial/errors.rst
diff options
context:
space:
mode:
authorIrit Katriel <1055913+iritkatriel@users.noreply.github.com>2022-04-20 12:43:10 (GMT)
committerGitHub <noreply@github.com>2022-04-20 12:43:10 (GMT)
commitf92bcfe6dea7d52dcc7077585d8818e8a0209604 (patch)
tree25831066371287d6dabe918eb2c27f6687726181 /Doc/tutorial/errors.rst
parentaaeea78b0f8f4c8dfab5cd4eb6fb4c5fe1ee21e2 (diff)
downloadcpython-f92bcfe6dea7d52dcc7077585d8818e8a0209604.zip
cpython-f92bcfe6dea7d52dcc7077585d8818e8a0209604.tar.gz
cpython-f92bcfe6dea7d52dcc7077585d8818e8a0209604.tar.bz2
gh-89770: [PEP-678] add exception notes to tutorial (GH-30441)
Diffstat (limited to 'Doc/tutorial/errors.rst')
-rw-r--r--Doc/tutorial/errors.rst64
1 files changed, 64 insertions, 0 deletions
diff --git a/Doc/tutorial/errors.rst b/Doc/tutorial/errors.rst
index 01fd762..57919e3 100644
--- a/Doc/tutorial/errors.rst
+++ b/Doc/tutorial/errors.rst
@@ -559,3 +559,67 @@ the following pattern::
... raise ExceptionGroup("Test Failures", excs)
...
+
+Enriching Exceptions with Notes
+===============================
+
+When an exception is created in order to be raised, it is usually initialized
+with information that describes the error that has occurred. There are cases
+where it is useful to add information after the exception was caught. For this
+purpose, exceptions have a method ``add_note(note)`` that accepts a string and
+adds it to the exception's notes list. The standard traceback rendering
+includes all notes, in the order they were added, after the exception. ::
+
+ >>> try:
+ ... raise TypeError('bad type')
+ ... except Exception as e:
+ ... e.add_note('Add some information')
+ ... e.add_note('Add some more information')
+ ... raise
+ ...
+ Traceback (most recent call last):
+ File "<stdin>", line 2, in <module>
+ TypeError: bad type
+ Add some information
+ Add some more information
+ >>>
+
+For example, when collecting exceptions into an exception group, we may want
+to add context information for the individual errors. In the following each
+exception in the group has a note indicating when this error has occurred. ::
+
+ >>> def f():
+ ... raise OSError('operation failed')
+ ...
+ >>> excs = []
+ >>> for i in range(3):
+ ... try:
+ ... f()
+ ... except Exception as e:
+ ... e.add_note(f'Happened in Iteration {i+1}')
+ ... excs.append(e)
+ ...
+ >>> raise ExceptionGroup('We have some problems', excs)
+ + Exception Group Traceback (most recent call last):
+ | File "<stdin>", line 1, in <module>
+ | ExceptionGroup: We have some problems (3 sub-exceptions)
+ +-+---------------- 1 ----------------
+ | Traceback (most recent call last):
+ | File "<stdin>", line 3, in <module>
+ | File "<stdin>", line 2, in f
+ | OSError: operation failed
+ | Happened in Iteration 1
+ +---------------- 2 ----------------
+ | Traceback (most recent call last):
+ | File "<stdin>", line 3, in <module>
+ | File "<stdin>", line 2, in f
+ | OSError: operation failed
+ | Happened in Iteration 2
+ +---------------- 3 ----------------
+ | Traceback (most recent call last):
+ | File "<stdin>", line 3, in <module>
+ | File "<stdin>", line 2, in f
+ | OSError: operation failed
+ | Happened in Iteration 3
+ +------------------------------------
+ >>>