[issue18776] atexit error display behavior changed in python 3

2013-10-13 Thread Antoine Pitrou
Antoine Pitrou added the comment: Since it's a regression from 2.7, I chose to commit it as a bugfix (to 3.3 and 3.4). -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed type: enhancement -> behavior ___ Python

[issue18776] atexit error display behavior changed in python 3

2013-10-13 Thread Roundup Robot
Roundup Robot added the comment: New changeset 19ce90930e8b by Antoine Pitrou in branch '3.3': Issue #18776: atexit callbacks now display their full traceback when they raise an exception. http://hg.python.org/cpython/rev/19ce90930e8b New changeset c13ef65f3dcf by Antoine Pitrou in branch 'defa

[issue18776] atexit error display behavior changed in python 3

2013-10-13 Thread Antoine Pitrou
Antoine Pitrou added the comment: Updated patch. -- stage: needs patch -> patch review versions: +Python 3.3 Added file: http://bugs.python.org/file32097/atexit_tracebacks2.patch ___ Python tracker

[issue18776] atexit error display behavior changed in python 3

2013-10-13 Thread Antoine Pitrou
Antoine Pitrou added the comment: > With your patch, can the SetTraceback in PyErr_Print be removed? I don't think so. PyErr_Print() calls sys.excepthook, which can be overriden with custom code. > Or should PyErr_Display only set the tb if there is none on the > object already? Well, why not!

[issue18776] atexit error display behavior changed in python 3

2013-10-13 Thread Georg Brandl
Georg Brandl added the comment: With your patch, can the SetTraceback in PyErr_Print be removed? Or should PyErr_Display only set the tb if there is none on the object already? -- ___ Python tracker ___

[issue18776] atexit error display behavior changed in python 3

2013-10-13 Thread Antoine Pitrou
Antoine Pitrou added the comment: Attached patch does the setting in PyErr_Display (which is an undocumented API, thus presumably private), and adds a test for atexit. -- Added file: http://bugs.python.org/file32095/atexit_tracebacks.patch ___ Python

[issue18776] atexit error display behavior changed in python 3

2013-10-13 Thread Georg Brandl
Georg Brandl added the comment: The attached patch fixes two instances of PyErr_Display being called without the traceback properly set on the exception object. -- keywords: +patch nosy: +georg.brandl, pitrou Added file: http://bugs.python.org/file32094/set_traceback.patch

[issue18776] atexit error display behavior changed in python 3

2013-08-23 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- stage: patch review -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue18776] atexit error display behavior changed in python 3

2013-08-18 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- components: +Library (Lib) keywords: +easy stage: -> patch review type: -> enhancement versions: -Python 3.1, Python 3.2, Python 3.3 ___ Python tracker

[issue18776] atexit error display behavior changed in python 3

2013-08-18 Thread Doug Hellmann
New submission from Doug Hellmann: Under python 2 when an atexit callback raised an exception the full traceback was displayed. Under python 3, only the summary of the exception is shown. Input file: import atexit def exit_with_exception(message): raise RuntimeError(message) atexit.regi