➜

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 benjamin.peterson
Recipients amaury.forgeotdarc, benjamin.peterson, eric.smith
Date 2008-05-06.21:58:50
SpamBayes Score 0.1472634
Marked as misclassified No
Message-id <1afaf6160805061458k3b85ef41ld276b53de15ea3ca@mail.gmail.com>
In-reply-to <1210110611.23.0.959001741141.issue2772@psf.upfronthosting.co.za>
Content 
On Tue, May 6, 2008 at 4:50 PM, Eric Smith <report@bugs.python.org> wrote:
>
>  Eric Smith <eric@trueblade.com> added the comment:
>
>  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 was just thinking that this problem would probably come up again.

>  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?

Well, the first thing to check for is Py_Py3kWarning. Then do the
extra logic and execution speed.
History
Date User Action Args
2008-05-06 21:58:52benjamin.petersonsetspambayes_score: 0.147263 -> 0.1472634
recipients: + benjamin.peterson, amaury.forgeotdarc, eric.smith
2008-05-06 21:58:51benjamin.petersonlinkissue2772 messages
2008-05-06 21:58:51benjamin.petersoncreate