[issue11654] errors in atexit hooks don't change process exit code

Glyph Lefkowitz added the comment: I hope nobody will mind if I close: It's a duplicate of issue1257 so future discussion, if any, should probably happen there. -- nosy: +glyph resolution: -> duplicate stage: -> resolved status: open -> closed

[issue11654] errors in atexit hooks don't change process exit code

hai shi added the comment: as antoine said in https://bugs.python.org/issue1257, this bug should be closed;) -- nosy: +shihai1991 ___ Python tracker ___

[issue11654] errors in atexit hooks don't change process exit code

ysj.ray ysj@gmail.com added the comment: see #1257 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11654 ___ ___ Python-bugs-list mailing

[issue11654] errors in atexit hooks don't change process exit code

Ray.Allen ysj@gmail.com added the comment: Comparing to the atexit() in C, I think this is the wrong behavior. I's weird that error in atexit does't change process exit code while error in common python code does. There should be a fix. -- nosy: +ysj.ray

[issue11654] errors in atexit hooks don't change process exit code

Ray.Allen ysj@gmail.com added the comment: A straight forward fix maybe making the interpreter exit code a static global variable and change it in Modules/atexitmodule.c:atexit_callfuncs() in the case of errors occurred. -- ___ Python tracker

[issue11654] errors in atexit hooks don't change process exit code

New submission from Antoine Pitrou pit...@free.fr: Not sure if it's the desired behaviour, so I'm reporting it: $ ./python -c import atexit; atexit.register(lambda: 1/0) echo success Error in atexit._run_exitfuncs: ZeroDivisionError: division by zero [36956 refs] success --