changeset: 71250:4e83d8f6d496 branch: 3.2 parent: 71242:b58b0c5c7e96 user: Victor Stinner date: Fri Jul 08 02:26:39 2011 +0200 files: Doc/ACKS.txt Doc/library/os.rst description: 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 -r b58b0c5c7e96 -r 4e83d8f6d496 Doc/ACKS.txt --- a/Doc/ACKS.txt Tue Jul 05 19:09:37 2011 -0700 +++ b/Doc/ACKS.txt Fri Jul 08 02:26:39 2011 +0200 @@ -105,6 +105,7 @@ * Robert Kern * Jim Kerr * Jan Kim + * Kamil Kisiel * Greg Kochanski * Guido Kollerie * Peter A. Koren @@ -142,7 +143,7 @@ * Ross Moore * Sjoerd Mullender * Dale Nagata - * Michal Nowikowski + * Michal Nowikowski * Ng Pheng Siong * Koray Oner * Tomas Oppelstrup diff -r b58b0c5c7e96 -r 4e83d8f6d496 Doc/library/os.rst --- a/Doc/library/os.rst Tue Jul 05 19:09:37 2011 -0700 +++ b/Doc/library/os.rst Fri Jul 08 02:26:39 2011 +0200 @@ -1582,8 +1582,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.