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 spiv
Recipients exarkun, neologix, r.david.murray, spiv
Date 2010-04-15.13:38:54
SpamBayes Score 1.8201067e-06
Marked as misclassified No
Message-id <>
Are there any platforms that define HAVE_SIGINTERRUPT but that do not define HAVE_SIGACTION?  If there are, then yes I expect they would fail that test.

It would be a shame to delay this fix just because it doesn't fix all platforms... is it possible to mark that test as a known failure on a platform with siginterrupt but without sigaction?

My initial comment outlined a change that would work for all platforms, but would be more complex.  (I think the signal_noreinstall.diff change would be good to make even with the more complex approach, though.)
Date User Action Args
2010-04-15 13:38:56spivsetrecipients: + spiv, exarkun, r.david.murray, neologix
2010-04-15 13:38:55spivsetmessageid: <>
2010-04-15 13:38:54spivlinkissue8354 messages
2010-04-15 13:38:54spivcreate