Message 150499 - Python tracker

Message150499

Author	pitrou
Recipients	jcea, meador.inge, pitrou, rbcollins
Date	2012-01-03.14:40:35
SpamBayes Score	6.6523594e-06
Marked as misclassified	No
Message-id	<1325601636.45.0.388769650609.issue13697@psf.upfronthosting.co.za>
In-reply-to

Content
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.

Content

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.

History
Date	User	Action	Args
2012-01-03 14:40:36	pitrou	set	recipients: + pitrou, jcea, rbcollins, meador.inge
2012-01-03 14:40:36	pitrou	set	messageid: <1325601636.45.0.388769650609.issue13697@psf.upfronthosting.co.za>
2012-01-03 14:40:35	pitrou	link	issue13697 messages
2012-01-03 14:40:35	pitrou	create