[issue10046] Correction to atexit documentation

Georg Brandl added the comment: Fixed in r85452. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bu

[issue10046] Correction to atexit documentation

Jason Baker added the comment: I like that phrasing. I think it would be a good idea to mention that this includes SIGINT by default, just to be explicit. -- ___ Python tracker __

[issue10046] Correction to atexit documentation

Georg Brandl added the comment: One could also argue that on SIGINT, the program is not "killed" but "interrupted" by the signal :) What about "... killed by an unhandled signal ..."? -- nosy: +georg.brandl ___ Python tracker

[issue10046] Correction to atexit documentation

Adam Olsen added the comment: Signals can directly kill a process. Try SIGTERM to see this. SIGINT is caught and handled by Python, which just happens to default to a graceful exit (unless stuck in a lib that prevents that.) Try pasting your script into an interactive interpreter session a

[issue10046] Correction to atexit documentation

R. David Murray added the comment: It is possible this behavior changed after the docs were written. I'm adding a couple of people to nosy who might have some insight into that possibility. It could be either a change in finalization procedures or a change in signal handling semantics, I th

[issue10046] Correction to atexit documentation

New submission from Jason Baker : There's an issue with the documentation on the atexit module[1]. It states: "Note: the functions registered via this module are not called when the program is killed by a signal, when a Python fatal internal error is detected, or when os._exit() is called."