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 gregory.p.smith
Recipients Rotem Yaari, Yury.Selivanov, georg.brandl, gregory.p.smith, gvanrossum, larry, ncoghlan, oconnor663, serhiy.storchaka, vstinner, yselivanov
Date 2016-06-14.16:06:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1465920372.07.0.0514101367582.issue25782@psf.upfronthosting.co.za>
In-reply-to
Content
I think I'm with Nick on this, the re-ordering fix is the closest to the right thing to do for 3.5 as it at least leaves all exceptions present in the chain.

As a more accurate long term fix, it would be great if we could express the tree via tuples in exception context in 3.6 or later.
History
Date User Action Args
2016-06-14 16:06:12gregory.p.smithsetrecipients: + gregory.p.smith, gvanrossum, georg.brandl, ncoghlan, vstinner, larry, Yury.Selivanov, serhiy.storchaka, yselivanov, oconnor663, Rotem Yaari
2016-06-14 16:06:12gregory.p.smithsetmessageid: <1465920372.07.0.0514101367582.issue25782@psf.upfronthosting.co.za>
2016-06-14 16:06:12gregory.p.smithlinkissue25782 messages
2016-06-14 16:06:11gregory.p.smithcreate