Skip to content

bpo-42179: Clarify exception chaining #23160

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
willingc merged 5 commits into from
Dec 16, 2020
Merged

bpo-42179: Clarify exception chaining #23160

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
86fe587
Update errors.rst
greatvovan Nov 5, 2020
c29f3a2
Update errors.rst
greatvovan Nov 5, 2020
35d34c3
Update errors.rst
greatvovan Nov 5, 2020
bb29890
Merge branch 'master' into bugfix/bpo-42179
greatvovan Nov 6, 2020
2831bc0
Update errors.rst
greatvovan Nov 9, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update errors.rst 
Remove mentioning of special attributes as folks think it's too much for beginners.
  • Loading branch information
@greatvovan
greatvovan authored Nov 9, 2020
commit 2831bc0c019daa2e3281fadbc9c56db92225024b
7 changes: 0 additions & 7 deletions Doc/tutorial/errors.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -312,13 +312,6 @@ disabled by using ``from None`` idiom:
File "<stdin>", line 4, in <module>
RuntimeError

There are two special attributes that enable chaining mechanics in
exceptions: ``__context__`` and ``__cause__``. When you raise an exception
inside :keyword:`except` or :keyword:`finally`, Pyhton automatically fills
``__context__`` attribute of the new exception with the caught one. When you
use ``from exc`` syntax, Pyhon fills ``__cause__`` attribute with
the ``exc``. You can use both attributes for introspection purposes, however
when formatting exception traceback message, ``__cause__`` takes priority.
For more information about chaining mechanics, see :ref:`bltin-exceptions`.


Expand Down