[issue12303] expose sigwaitinfo() and sigtimedwait() in the signal module

[STINNER Victor]

STINNER Victor <victor.stinner at haypocalc.com> added the comment:

> test_sigwaitinfo_interrupted() fails because SIGALRM
> signal handler is called ...

Oh, the problem is that sigwait() behaviour changes after a fork: it is interrupted if an unexpected signal is received, but the signal handler is not called. It behaves correctly (the signal handler is called) without the fork.

The correct fix is maybe to avoid the os.fork() instead of skipping the test on FreeBSD 6.

----------
nosy: +neologix
stage: patch review -> commit review

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue12303>
_______________________________________