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 ncoghlan
Recipients Arfrever, benjamin.peterson, georg.brandl, ncoghlan, pitrou
Date 2012-02-28.02:28:40
SpamBayes Score 0.009214984
Marked as misclassified No
Message-id <1330396122.0.0.206083394528.issue14133@psf.upfronthosting.co.za>
In-reply-to
Content
The alternatives are a backwards compatibility break (i.e. raise exc from other_exc would suppress the context, but exc.__cause__ = other_exc would not) or else that we don't succeed in eliminating the dual use of __cause__ in the display routines.

Given that those two problems are the reason I went for the PEP 409 approach in the first place, I'm really only interested in alternative approaches that eliminate them (such as setting the flag automatically whenever __cause__ is set). If you don't like it, then we already have PEP 409's Ellipsis based implementation which meets my criteria.
History
Date User Action Args
2012-02-28 02:28:42ncoghlansetrecipients: + ncoghlan, georg.brandl, pitrou, benjamin.peterson, Arfrever
2012-02-28 02:28:41ncoghlansetmessageid: <1330396122.0.0.206083394528.issue14133@psf.upfronthosting.co.za>
2012-02-28 02:28:41ncoghlanlinkissue14133 messages
2012-02-28 02:28:40ncoghlancreate