From 8703be94b197ca7fdec8270705bbfefae232ee5b Mon Sep 17 00:00:00 2001 From: Victor Stinner Date: Fri, 8 Jul 2011 02:14:55 +0200 Subject: 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. --- 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 index 2aa0316..58896b0 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 c2ea1be..c6e32f6 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. -- cgit v0.12