Author vilya
Recipients flox, neologix, petri.lehtinen, vilya, vstinner
Date 2011-11-03.14:12:14
SpamBayes Score 0.000234314
Marked as misclassified No
Message-id <1320329535.16.0.044014019649.issue13285@psf.upfronthosting.co.za>
In-reply-to
Content
Petri: yes, that what I was suggesting.

Charles-François: I'm certainly open to alternatives. Unless I've overlooked something though, the problem is that no workaround is possible at the moment. BTW this came up in the context of a customer script for the software I work on, so it's not just a theoretical problem - at least, not for me. :-)

I guess another solution would be methods to save and restore the native signal handers, e.g. savesignal(signum) & restoresignal(signum). That wouldn't entirely solve the problem - if someone called setsignal() before calling savesignal(), they'd end up in the same situation - but it would at least permit a workaround.
History
Date User Action Args
2011-11-03 14:12:15vilyasetrecipients: + vilya, vstinner, flox, neologix, petri.lehtinen
2011-11-03 14:12:15vilyasetmessageid: <1320329535.16.0.044014019649.issue13285@psf.upfronthosting.co.za>
2011-11-03 14:12:14vilyalinkissue13285 messages
2011-11-03 14:12:14vilyacreate