[Python-checkins] cpython (2.7): Issue #12423: Fix os.abort() documentation

[victor.stinner]

http://hg.python.org/cpython/rev/1ac21a715c5d
changeset:   71249:1ac21a715c5d
branch:      2.7
user:        Victor Stinner <victor.stinner at haypocalc.com>
date:        Fri Jul 08 02:14:55 2011 +0200
summary:
  Issue #12423: Fix os.abort() documentation

The Python signal handler for SIGABRT is not called on os.abort() (only if the
signal is raised manually or sent by another process). Patch by Kamil Kisiel.

files:
  Doc/ACKS.txt       |  3 ++-
  Doc/library/os.rst |  5 +++--
  2 files changed, 5 insertions(+), 3 deletions(-)


diff --git a/Doc/ACKS.txt b/Doc/ACKS.txt
--- a/Doc/ACKS.txt
+++ b/Doc/ACKS.txt
@@ -103,6 +103,7 @@
    * Robert Kern
    * Jim Kerr
    * Jan Kim
+   * Kamil Kisiel
    * Greg Kochanski
    * Guido Kollerie
    * Peter A. Koren
@@ -139,7 +140,7 @@
    * Ross Moore
    * Sjoerd Mullender
    * Dale Nagata
-   * Michal Nowikowski 
+   * Michal Nowikowski
    * Ng Pheng Siong
    * Koray Oner
    * Tomas Oppelstrup
diff --git a/Doc/library/os.rst b/Doc/library/os.rst
--- a/Doc/library/os.rst
+++ b/Doc/library/os.rst
@@ -1666,8 +1666,9 @@
 
    Generate a :const:`SIGABRT` signal to the current process.  On Unix, the default
    behavior is to produce a core dump; on Windows, the process immediately returns
-   an exit code of ``3``.  Be aware that programs which use :func:`signal.signal`
-   to register a handler for :const:`SIGABRT` will behave differently.
+   an exit code of ``3``.  Be aware that calling this function will not call the
+   Python signal handler registered for :const:`SIGABRT` with
+   :func:`signal.signal`.
 
    Availability: Unix, Windows.
 

-- 
Repository URL: http://hg.python.org/cpython