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.18:26:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1524421601.39.0.682650639539.issue33329@psf.upfronthosting.co.za>
In-reply-to
Content
One option would be to create a list of possible defined signals and check if the signal is on the list.  For realtime signals, it just a matter to check if SIGRTMIN <= signal <= SIGRTMAX.

The glibc defined signals can be checked at tst-signal.c [1] or from main signal(7).  It should cover usual ISO C, POSIX, and some linux arch-specific signals, but you will still need to check if other OS defined extra signals uses elsewhere (another option would to add this check only for Linux/glibc).

[1] https://sourceware.org/git/?p=glibc.git;a=blob;f=signal/tst-sigset.c;h=a2b764de5ad66ee960c94ec18df75a07fce4b9a6;hb=HEAD
History
Date User Action Args
2018-04-22 18:26:41azanellasetrecipients: + azanella, pitrou, ned.deily, hroncok
2018-04-22 18:26:41azanellasetmessageid: <1524421601.39.0.682650639539.issue33329@psf.upfronthosting.co.za>
2018-04-22 18:26:41azanellalinkissue33329 messages
2018-04-22 18:26:41azanellacreate