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 kristjan.jonsson
Recipients amaury.forgeotdarc, kristjan.jonsson, loewis, mhammond
Date 2009-01-19.21:06:36
SpamBayes Score 0.0070681255
Marked as misclassified No
Message-id <>
Here is what I think is a better attempt at the selective-disabling.  I 
did away with the messy macros and added a function in errors.c.  This 
maintans a global 'level' variable, implicitly guarded by the GIL.  Now 
only the thread that first enters a guarded block will set the hendler, 
and the thread that is last to leave will reset it.  This should 
guarantee that between the two macros, our custom handler is set, and 
that no thread pulls the rug from underneath another.
Date User Action Args
2009-01-19 21:06:47kristjan.jonssonsetrecipients: + kristjan.jonsson, loewis, mhammond, amaury.forgeotdarc
2009-01-19 21:06:45kristjan.jonssonsetmessageid: <>
2009-01-19 21:06:44kristjan.jonssonlinkissue4804 messages
2009-01-19 21:06:43kristjan.jonssoncreate