Kristján Valur Jónsson <krist...@ccpgames.com> added the comment: 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.
Added file: http://bugs.python.org/file12802/crterror.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue4804> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
