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 pitrou
Recipients barry, ncoghlan, pitrou
Date 2008-12-02.14:33:58
SpamBayes Score 0.0011773027
Marked as misclassified No
Message-id <1228228439.08.0.282233941417.issue4486@psf.upfronthosting.co.za>
In-reply-to
Content
The current behaviour is the result of how I interpreted the error
reporting specification in PEP 3134. See "Enhanced Reporting" in
http://www.python.org/dev/peps/pep-3134/ . I may have misinterpreted it,
in that both the cause and the context are printed out while the PEP may
be read as suggesting the context must not be printed out when there is
a cause.

In any case, I don't think it is a release blocker. It only regards a
new and advanced feature (explicit exception chaining) and doesn't
disrupt its functioning.
History
Date User Action Args
2008-12-02 14:33:59pitrousetrecipients: + pitrou, barry, ncoghlan
2008-12-02 14:33:59pitrousetmessageid: <1228228439.08.0.282233941417.issue4486@psf.upfronthosting.co.za>
2008-12-02 14:33:58pitroulinkissue4486 messages
2008-12-02 14:33:58pitroucreate