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
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
nosy: -BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1257
___
___
Changes by Doug Hellmann doug.hellm...@gmail.com:
--
nosy: +doughellmann
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1257
___
___
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
Changes by Christian Heimes li...@cheimes.de:
--
assignee: christian.heimes -
versions: +Python 3.4 -Python 2.7, Python 3.1, Python 3.2, Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1257
ysj.ray ysj@gmail.com 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
Amaury Forgeot d'Arc amaur...@gmail.com 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 rep...@bugs.python.org
Mark Lawrence breamore...@yahoo.co.uk 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
Changes by Terry J. Reedy tjre...@udel.edu:
--
versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.4, Python 2.5, Python
3.0
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1257
___
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]
http://bugs.python.org/issue1257
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
Christian Heimes added the comment:
The issue should be addressed in the C code.
--
assignee: - gvanrossum
nosy: +gvanrossum, tiran
priority: - normal
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1257
__
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
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 #
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 =
15 matches
Mail list logo