From: Victor Stinner <victor.stinner@haypocalc.com>
Date: Fri, 8 Jul 2011 00:14:55 +0000 (+0200)
Subject: Issue #12423: Fix os.abort() documentation
X-Git-Tag: v2.7.3rc1~627
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=8703be94b197ca7fdec8270705bbfefae232ee5b;p=thirdparty%2FPython%2Fcpython.git

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.
---

diff --git a/Doc/ACKS.txt b/Doc/ACKS.txt
index 2aa031607e14..58896b0e7967 100644
--- a/Doc/ACKS.txt
+++ b/Doc/ACKS.txt
@@ -103,6 +103,7 @@ docs@python.org), and we'll be glad to correct the problem.
    * Robert Kern
    * Jim Kerr
    * Jan Kim
+   * Kamil Kisiel
    * Greg Kochanski
    * Guido Kollerie
    * Peter A. Koren
@@ -139,7 +140,7 @@ docs@python.org), and we'll be glad to correct the problem.
    * 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
index c2ea1be951bb..c6e32f66a34f 100644
--- a/Doc/library/os.rst
+++ b/Doc/library/os.rst
@@ -1666,8 +1666,9 @@ to be ignored.
 
    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.