Comment 3 for bug 173007

I'm not actively working on this anymore. There's a fundamental trade-off between risking EINTR vs. being able to interrupt code blocked in e.g. a read call. Arguably the status quo is better, as at least you get a pdb prompt pretty reliably, whereas if we use siginterrupt then a process stuck in a read call that never returns will never act on a SIGQUIT signal. As an added complication signal.siginterrupt was actually mostly broken until Python 2.6.3 or thereabouts.

It would be nice to do something about this, but I'm not sure what, and I'm not likely to spend time thinking about this for the foreseeable future.