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 rbcollins
Recipients berker.peksag, rbcollins, serhiy.storchaka
Date 2015-07-25.18:49:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1437850154.7.0.0732439310477.issue24710@psf.upfronthosting.co.za>
In-reply-to
Content
We can't use from_exception in __init__ because from_exception's job is to look up __traceback__, but the legacy API allows arbitrary tb objects which may not be exc.__traceback__, and modifying exc.__traceback__ or creating a shim object just to be able to use from_exception doesn't make sense to me.

This patch looks good, and I'm applying to 3.6. It has no functional impact (except for perhaps weird mocking corner cases, but as its a pure class that shouldn't be needed), so I'm leaving it out of 3.5, since i'm not 100% sure where the move to a new repo is at, and its not worth figuring that out.
History
Date User Action Args
2015-07-25 18:49:14rbcollinssetrecipients: + rbcollins, berker.peksag, serhiy.storchaka
2015-07-25 18:49:14rbcollinssetmessageid: <1437850154.7.0.0732439310477.issue24710@psf.upfronthosting.co.za>
2015-07-25 18:49:14rbcollinslinkissue24710 messages
2015-07-25 18:49:14rbcollinscreate