[issue1257] atexit errors should result in nonzero exit code

STINNER Victor added the comment: Antoine disagrees with the feature request, so I close it. You can modify your atexit callbacks to catch exceptions and decide how to handle them: write them into a file, into stderr, etc. -- nosy: +vstinner resolution: -> rejected stage: patch revi

[issue1257] atexit errors should result in nonzero exit code

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue1257] atexit errors should result in nonzero exit code

Antoine Pitrou added the comment: I would disagree with this report. There are many errors which are effectively silenced by Python, except for being printed on stderr: for example, errors which occur in a __del__ method or a weakref callback (both of which semantically similar to an atexit ha

[issue1257] atexit errors should result in nonzero exit code

Changes by Doug Hellmann : -- nosy: +doughellmann ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue1257] atexit errors should result in nonzero exit code

Changes by Christian Heimes : -- assignee: christian.heimes -> versions: +Python 3.4 -Python 2.7, Python 3.1, Python 3.2, Python 3.3 ___ Python tracker ___ __

[issue1257] atexit errors should result in nonzero exit code

ysj.ray added the comment: I think there is no need to implement this in python2.x since it's a behavior change which could introduce some compatibility issues to someone's code, besides in 2.x both sys.exitfunc and atexit module should be considered, that makes the code looks complex. The s

[issue1257] atexit errors should result in nonzero exit code

Amaury Forgeot d'Arc added the comment: exit code = 128 + # of failed atexits I don't agree with the feature. Do we need something so complex? -- nosy: +amaury.forgeotdarc ___ Python tracker __

[issue1257] atexit errors should result in nonzero exit code

Mark Lawrence added the comment: Can someone please review the attached patch with a view to committing, it contains doc and unit test changes. -- nosy: +BreamoreBoy stage: -> patch review versions: -Python 2.6 ___ Python tracker

[issue1257] atexit errors should result in nonzero exit code

Changes by Terry J. Reedy : -- versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.4, Python 2.5, Python 3.0 ___ Python tracker ___ __

[issue1257] atexit errors should result in nonzero exit code

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: I'm assigning this to Christian because he was doing the GHOP review. -- assignee: gvanrossum -> christian.heimes nosy: +benjamin.peterson __ Tracker <[EMAIL PROTECTED]>

[issue1257] atexit errors should result in nonzero exit code

Titus Brown added the comment: Please see GHOP patches by [EMAIL PROTECTED], http://code.google.com/p/google-highly-open-participation-psf/issues/detail?id=215 I've attached the Python 2.6 patch here. -- nosy: +titus Added file: http://bugs.python.org/file9104/ghop-215-py2.6-ctb.diff

[issue1257] atexit errors should result in nonzero exit code

Christian Heimes added the comment: The issue should be addressed in the C code. -- assignee: -> gvanrossum nosy: +gvanrossum, tiran priority: -> normal __ Tracker <[EMAIL PROTECTED]> __

[issue1257] atexit errors should result in nonzero exit code

Lakin Wecker added the comment: sorry for the noise and duplication. The full code listing should have been: 46 # Sometimes an exception happens during exit, try to make sure we get 47 # a non_zero exit code. 48 old_exitfunc =

[issue1257] atexit errors should result in nonzero exit code

Lakin Wecker added the comment: I am an agreeance with the original report. I just finished writing an automated test that did the following to work around this behavior: 46 # Sometimes an exception happens during exit, try to make sure we get 47 #

[issue1257] atexit errors should result in nonzero exit code

New submission from Robert Brewer : While debugging/fixing the logging module's atexit behavior (see http://www.cherrypy.org/ticket/646 -- it chokes atexit if stdout is closed), it became difficult to write an automated test