cpython: 4e83d8f6d496 (original) (raw)

Mercurial > cpython

changeset 71250:4e83d8f6d496 3.2

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. [#12423]

Victor Stinner victor.stinner@haypocalc.com
date	Fri, 08 Jul 2011 02:26:39 +0200
parents	b58b0c5c7e96
children	e3c115ba8dc0 52ed0c6bb461
files	Doc/ACKS.txt Doc/library/os.rst
diffstat	2 files changed, 5 insertions(+), 3 deletions(-)[+] [-] Doc/ACKS.txt 3 Doc/library/os.rst 5

line wrap: on

line diff

--- a/Doc/ACKS.txt +++ b/Doc/ACKS.txt @@ -105,6 +105,7 @@ docs@python.org), and we'll be glad to c * Robert Kern * Jim Kerr * Jan Kim

- Kamil Kisiel
- Greg Kochanski
- Guido Kollerie
- Peter A. Koren @@ -142,7 +143,7 @@ docs@python.org), and we'll be glad to c
- Ross Moore
- Sjoerd Mullender
- Dale Nagata

- Michal Nowikowski

- Michal Nowikowski
- Ng Pheng Siong
- Koray Oner
- Tomas Oppelstrup

--- a/Doc/library/os.rst +++ b/Doc/library/os.rst @@ -1582,8 +1582,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.