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, poke
Date 2012-03-16.12:24:27
SpamBayes Score 2.0088764e-11
Marked as misclassified No
Message-id <1331900668.46.0.923989354795.issue14133@psf.upfronthosting.co.za>
In-reply-to
Content
With the decision on whether or not to suppress the context moved out to a separate flag, I think we need to allow it. Requiring that the flag be False *and* that the context also be None gets us back to asking the question of why the flag doesn't work when the context is set to a different value. That question was part of the genesis of the Ellipsis-as-sentinel approach in the original 409 implementation.

I wouldn't stress too much about the formatting though. Perhaps note in the suppress context docs that the output can get *very* noisy if you turn it off when both cause and context are set, so while it does display all the exception information, the default output isn't going to be very easy to read.
History
Date User Action Args
2012-03-16 12:24:28ncoghlansetrecipients: + ncoghlan, georg.brandl, pitrou, benjamin.peterson, Arfrever, poke
2012-03-16 12:24:28ncoghlansetmessageid: <1331900668.46.0.923989354795.issue14133@psf.upfronthosting.co.za>
2012-03-16 12:24:27ncoghlanlinkissue14133 messages
2012-03-16 12:24:27ncoghlancreate