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

Charles-François Natali report at bugs.python.org
Wed Jun 29 09:29:10 CEST 2011


Charles-François Natali <neologix at free.fr> added the comment:

> 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.
>

Reminds me of http://bugs.python.org/issue8407#msg138066

But I think we could just remove this test: honestly, I'm not sure
that checking the behavior in case of delivery of an unblocked signal
is really useful, especially since the behavior is not clearly
defined, see POSIX man page:
"""
The sigwaitinfo() and sigtimedwait() functions may fail if:

[EINTR]
The wait was interrupted by an unblocked, caught signal. It will be
documented in system documentation whether this error will cause these
functions to fail.
"""

"may fail" [...] "It will be documented in system documentation"

----------

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


More information about the Python-bugs-list mailing list