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 r.david.murray
Recipients Carlos Pita, neologix, r.david.murray
Date 2015-03-22.05:06:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1427000815.7.0.158289486656.issue23735@psf.upfronthosting.co.za>
In-reply-to
Content
If it used to handle the signal and then re-raise it, why doesn't it now set its flag and then re-raise the signal?  (I also don't understand why the API isn't that the application takes back the signal handler if it needs it if it is using readline, but I'm not familiar enough with signal handling in applications to really judge that, I suppose.)

However, we certainly understand the issues with doing too much in signal handlers, so if that ship has sailed I guess we'll just have to deal with it.
History
Date User Action Args
2015-03-22 05:06:55r.david.murraysetrecipients: + r.david.murray, neologix, Carlos Pita
2015-03-22 05:06:55r.david.murraysetmessageid: <1427000815.7.0.158289486656.issue23735@psf.upfronthosting.co.za>
2015-03-22 05:06:55r.david.murraylinkissue23735 messages
2015-03-22 05:06:55r.david.murraycreate