bpo-42179: Clarify exception chaining (GH-23160)
* Update errors.rst
Clarify exception chaining behaviour and give a reference to the library documentation.
* Update errors.rst
Wording
* Update errors.rst
Spelling
* Update errors.rst
Remove mentioning of special attributes as folks think it's too much for beginners.
diff --git a/Doc/tutorial/errors.rst b/Doc/tutorial/errors.rst
index efe44da..4a25861 100644
--- a/Doc/tutorial/errors.rst
+++ b/Doc/tutorial/errors.rst
@@ -281,17 +281,17 @@
This can be useful when you are transforming exceptions. For example::
>>> def func():
- ... raise IOError
+ ... raise ConnectionError
...
>>> try:
... func()
- ... except IOError as exc:
+ ... except ConnectionError as exc:
... raise RuntimeError('Failed to open database') from exc
...
Traceback (most recent call last):
File "<stdin>", line 2, in <module>
File "<stdin>", line 2, in func
- OSError
+ ConnectionError
<BLANKLINE>
The above exception was the direct cause of the following exception:
<BLANKLINE>
@@ -300,7 +300,7 @@
RuntimeError: Failed to open database
Exception chaining happens automatically when an exception is raised inside an
-:keyword:`except` or :keyword:`finally` section. Exception chaining can be
+:keyword:`except` or :keyword:`finally` section. This can be
disabled by using ``from None`` idiom:
>>> try: