Message 66337 - Python tracker

➜

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	eric.smith
Recipients	amaury.forgeotdarc, benjamin.peterson, eric.smith
Date	2008-05-06.21:50:08
SpamBayes Score	0.23586869
Marked as misclassified	No
Message-id	<1210110611.23.0.959001741141.issue2772@psf.upfronthosting.co.za>
In-reply-to

Content
Since we're just trying to prevent this function from recursing (indirectly) into itself, I think all of the logic can go here. What would you suggest the function _PyErr_InErrorProcessing do differently? I think the real issue is: Does the additional logic and execution time involved in adding per-thread state justify being "more correct", or can we occasionally lose a warning message?

Since we're just trying to prevent this function from recursing
(indirectly) into itself, I think all of the logic can go here.

What would you suggest the function _PyErr_InErrorProcessing do differently?

I think the real issue is:  Does the additional logic and execution time
involved in adding per-thread state justify being "more correct", or can
we occasionally lose a warning message?

History
Date	User	Action	Args
2008-05-06 21:50:11	eric.smith	set	spambayes_score: 0.235869 -> 0.23586869 recipients: + eric.smith, amaury.forgeotdarc, benjamin.peterson
2008-05-06 21:50:11	eric.smith	set	spambayes_score: 0.235869 -> 0.235869 messageid: <1210110611.23.0.959001741141.issue2772@psf.upfronthosting.co.za>
2008-05-06 21:50:10	eric.smith	link	issue2772 messages
2008-05-06 21:50:09	eric.smith	create