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 azanella
Recipients azanella, hroncok, ned.deily, pitrou
Date 2018-04-22.13:56:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Why not export and use the canonical way of sigemptyset/sigfillset/sigaddset/sigdelset/sigismember instead of pushing for more potential non-conformant code? For glibc sigfillset will correctly fill all the signal set structure while removing the internal used signals. This is par what POSIX specifies [1] where it states that: 

'either sigemptyset() or sigfillset() must be called prior to any other use of the signal set'

And more importantly:

'For example, blocking or ignoring an implementation-defined signal may have undesirable side-effects, whereas the default action for that signal is harmless. In such a case, it would be preferable for such a signal to be excluded from the signal set returned by sigfillset().'

Also keep that since is an implementation detail, different libcs can use different internal signals. UCLIBC, for instance, uses the same 2 signals as GLIBC, however MUSL allocates signal 32, 33, and 34 for internal usage (and excludes in sigfillset and warns with EINVAL on sigaddset). 

Date User Action Args
2018-04-22 13:56:37azanellasetrecipients: + azanella, pitrou, ned.deily, hroncok
2018-04-22 13:56:37azanellasetmessageid: <>
2018-04-22 13:56:37azanellalinkissue33329 messages
2018-04-22 13:56:36azanellacreate