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 rhettinger
Recipients cool-RR, rhettinger
Date 2020-02-21.20:00:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1582315232.59.0.621263718222.issue39717@roundup.psfhosted.org>
In-reply-to
Content
What do you think it is necessary to switch from implicit chaining to explicit chaining?

If anyone is currently relying on __context__ vs __cause__, this patch will break their code.

In a traceback, the only visible difference is in the text between the exceptions:

- During handling of the above exception, another exception occurred:
+ The above exception was the direct cause of the following exception:

While we haven't been 100% consistent about this, the norm has been to either use implicit chaining or use "from None" to turn-off chaining.  The "from e" approach can be used to alter the explicit chain, perhaps skipping over one or more exceptions, but that isn't the case here.
History
Date User Action Args
2020-02-21 20:00:32rhettingersetrecipients: + rhettinger, cool-RR
2020-02-21 20:00:32rhettingersetmessageid: <1582315232.59.0.621263718222.issue39717@roundup.psfhosted.org>
2020-02-21 20:00:32rhettingerlinkissue39717 messages
2020-02-21 20:00:32rhettingercreate