SIGTERM is no longer caught to call sys.exitfunc.

This change was made long ago but the documentation was never updated.

2 files changed, 5 insertions, 7 deletions

diff --git a/Doc/lib/libsignal.tex b/Doc/lib/libsignal.tex
index 94ad536..f2624e6 100644
--- a/Doc/lib/libsignal.tex
+++ b/Doc/lib/libsignal.tex
@@ -42,10 +42,8 @@ catch synchronous errors like \constant{SIGFPE} or \constant{SIGSEGV}.
 \item
 Python installs a small number of signal handlers by default:
 \constant{SIGPIPE} is ignored (so write errors on pipes and sockets can be
-reported as ordinary Python exceptions), \constant{SIGINT} is translated
-into a \exception{KeyboardInterrupt} exception, and \constant{SIGTERM} is
-caught so that necessary cleanup (especially \code{sys.exitfunc}) can
-be performed before actually terminating.  All of these can be
+reported as ordinary Python exceptions) and \constant{SIGINT} is translated
+into a \exception{KeyboardInterrupt} exception.  All of these can be
 overridden.
 
 \item
diff --git a/Doc/lib/libsys.tex b/Doc/lib/libsys.tex
index 76b54a3..afb4008 100644
--- a/Doc/lib/libsys.tex
+++ b/Doc/lib/libsys.tex
@@ -122,9 +122,9 @@ way to exit a program when an error occurs.
   This value is not actually defined by the module, but can be set by
   the user (or by a program) to specify a clean-up action at program
   exit.  When set, it should be a parameterless function.  This function
-  will be called when the interpreter exits in any way (except when a
-  fatal error occurs: in that case the interpreter's internal state
-  cannot be trusted).
+  will be called when the interpreter exits.  Note: the exit function
+  is not called when the program is killed by a signal, when a Python
+  fatal internal error is detected, or when \code{os._exit()} is called.
 \end{datadesc}
 
 \begin{funcdesc}{getrefcount}{object}