This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Niels Albers
Recipients Niels Albers, docs@python, rhettinger, shireenrao
Date 2019-09-05.06:15:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thanks Srinivas for the suggestion. IMO exception chaining has more utility than only dealing with new exceptions that are caused by exception handling. It's all about preserving exception context. As both a writer of libraries and a user of such, I do like to have a full context chain when I have to handle an exception (or more importantly as a devops engineeer: log it)

Is this edit acceptable?

"If you need to track exception context, you can use exception chaining. You can chain exceptions by using the ``from`` clause. Just raise a new exception class or instance from an existing exception. The existing exception will be set as 
the cause for the new exception."
Date User Action Args
2019-09-05 06:15:34Niels Alberssetrecipients: + Niels Albers, rhettinger, docs@python, shireenrao
2019-09-05 06:15:34Niels Alberssetmessageid: <>
2019-09-05 06:15:33Niels Alberslinkissue37891 messages
2019-09-05 06:15:33Niels Alberscreate