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 brett.cannon
Recipients brett.cannon
Date 2016-02-18.22:59:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1455836350.85.0.0162824201978.issue26389@psf.upfronthosting.co.za>
In-reply-to
Content
When reading https://docs.python.org/3/library/traceback.html#traceback.print_exception I noticed that everything takes a traceback or a set of exception type, instance, and traceback. But since Python 3.0 all of that information is contained in a single exception object. So there's no reason to expand the APIs in the traceback module that take an exception to just take an exception instance and infer the exception type and grab the exception from exception instance itself.
History
Date User Action Args
2016-02-18 22:59:10brett.cannonsetrecipients: + brett.cannon
2016-02-18 22:59:10brett.cannonsetmessageid: <1455836350.85.0.0162824201978.issue26389@psf.upfronthosting.co.za>
2016-02-18 22:59:10brett.cannonlinkissue26389 messages
2016-02-18 22:59:10brett.cannoncreate