From: Guido van Rossum <guido@python.org>
Date: Mon, 12 Feb 1996 23:18:51 +0000 (+0000)
Subject: document non-BSD SIGCHLD behaviour
X-Git-Tag: v1.4b1~364
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=c1715527fd0e55b90f21580410a4505414acebf1;p=thirdparty%2FPython%2Fcpython.git

document non-BSD SIGCHLD behaviour
---

diff --git a/Doc/lib/libsignal.tex b/Doc/lib/libsignal.tex
index 63b671f95abf..802c4d107f18 100644
--- a/Doc/lib/libsignal.tex
+++ b/Doc/lib/libsignal.tex
@@ -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
diff --git a/Doc/libsignal.tex b/Doc/libsignal.tex
index 63b671f95abf..802c4d107f18 100644
--- a/Doc/libsignal.tex
+++ b/Doc/libsignal.tex
@@ -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