document non-BSD SIGCHLD behaviour

This commit is contained in:
Guido van Rossum 1996-02-12 23:18:51 +00:00
parent 789742b8f8
commit c1715527fd
2 changed files with 8 additions and 2 deletions

View File

@ -8,7 +8,10 @@ Some general rules for working with signals handlers:
\item
A handler for a particular signal, once set, remains installed until
it is explicitly reset (i.e. Python uses the BSD style interface).
it is explicitly reset (i.e. Python emulates the BSD style interface
regardless of the underlying implementation), with the exception of
the handler for \code{SIGCHLD}, which follows the underlying
implementation.
\item
There is no way to ``block'' signals temporarily from critical

View File

@ -8,7 +8,10 @@ Some general rules for working with signals handlers:
\item
A handler for a particular signal, once set, remains installed until
it is explicitly reset (i.e. Python uses the BSD style interface).
it is explicitly reset (i.e. Python emulates the BSD style interface
regardless of the underlying implementation), with the exception of
the handler for \code{SIGCHLD}, which follows the underlying
implementation.
\item
There is no way to ``block'' signals temporarily from critical