Antoine Pitrou <pit...@free.fr> added the comment: Yes, using synchronization primitives or doing I/O in Python signal handlers isn't a good idea. Perhaps the signal docs should be clearer about that.
> Of course, this wasn't ever safe code, and we're changing it (to have the > signal handler merely set a integer flag that the logging handler can consult > without locking) Indeed, setting a variable (or using set_wakeup_fd()) is the right approach. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13697> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
