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 amaury.forgeotdarc, benjamin.peterson, pitrou, vstinner
Date 2008-08-22.10:22:06
SpamBayes Score 1.9640918e-06
Marked as misclassified No
Message-id <1219400530.32.0.747338490815.issue3611@psf.upfronthosting.co.za>
In-reply-to
Content
Agreed with Amaury, it's not PyErr_SetObject's job to try to
save/restore the tstate->exc_* variables. We'll probably have to live
with the small context-losing glitches in 3.0.

For 3.1, a radical solution would be to drop the "exception
normalization" misfeature (which is a source of complications and
potential bugs) and always instantiate exception objects as soon as they
are raised rather than lazily. We need to make sure the performance loss
is reasonable though.
History
Date User Action Args
2008-08-22 10:22:10pitrousetrecipients: + pitrou, amaury.forgeotdarc, vstinner, benjamin.peterson
2008-08-22 10:22:10pitrousetmessageid: <1219400530.32.0.747338490815.issue3611@psf.upfronthosting.co.za>
2008-08-22 10:22:09pitroulinkissue3611 messages
2008-08-22 10:22:06pitroucreate