Ronald Oussoren <ronaldousso...@mac.com> added the comment:

The documentation for the SIG* constants also mentions:

----
SIG*
All the signal numbers are defined symbolically. For example, the hangup signal 
is defined as signal.SIGHUP; the variable names are identical to the names used 
in C programs, as found in <signal.h>. The Unix man page for ‘signal()’ lists 
the existing signals (on some systems this is signal(2), on others the list is 
in signal(7)). Note that not all systems define the same set of signal names; 
only those names defined by the system are defined by this module.
----

This is however mentioned halfway through the list of constants.  I'm not sure 
why this is so, IMHO it would be clearer to move the fragment I quote to the 
start of the module constants section.

We shouldn't define SIGCLD on platforms that don't have this name available in 
their libc headers, which includes macOS.  If the fragment above were moved to 
the start of the section no further updates would be required (IMHO).

----------
components: +macOS
nosy: +ned.deily, ronaldoussoren

_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue45251>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to