[issue7317] Display full tracebacks when an error occurs asynchronously

Andrew Svetlov added the comment: Committed. Thanks, guys! -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue7317] Display full tracebacks when an error occurs asynchronously

Roundup Robot added the comment: New changeset a281604a5c9a by Andrew Svetlov in branch 'default': Issue #7317: Display full tracebacks when an error occurs asynchronously. http://hg.python.org/cpython/rev/a281604a5c9a -- nosy: +python-dev ___ Python

[issue7317] Display full tracebacks when an error occurs asynchronously

Alexey Kachayev added the comment: Updated test case for traceback printing, fixed test_cmd_line crashing with new ignored exception message formatting (test was based on regular expression). Patch is attached. -- nosy: +kachayev Added file: http://bugs.python.org/file27853/issue7317.d

[issue7317] Display full tracebacks when an error occurs asynchronously

Changes by Martin Panter : -- nosy: +vadmium ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue7317] Display full tracebacks when an error occurs asynchronously

Changes by Andrew Svetlov : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue7317] Display full tracebacks when an error occurs asynchronously

alon horev added the comment: Hi Antoine, can you please have a look at the patch? It's been over a year since it's submitted. (-: thanks! -- ___ Python tracker ___ _

[issue7317] Display full tracebacks when an error occurs asynchronously

Changes by Antoine Pitrou : -- Removed message: http://bugs.python.org/msg167273 ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue7317] Display full tracebacks when an error occurs asynchronously

Antoine Pitrou added the comment: Oops, sorry for the silence, I had forgotten about this issue. I'll take a look at the patch soon. -- ___ Python tracker ___ ___

[issue7317] Display full tracebacks when an error occurs asynchronously

Antoine Pitrou added the comment: Oops, sorry for the silence, I had forgotten about this issue. I'll take a look at the patch soon. -- ___ Python tracker ___ ___

[issue7317] Display full tracebacks when an error occurs asynchronously

alon horev added the comment: how does one get his patch reviewed? (it's been 6 months) -- ___ Python tracker ___ ___ Python-bugs-list

[issue7317] Display full tracebacks when an error occurs asynchronously

Changes by Éric Araujo : -- keywords: +needs review priority: high -> normal stage: needs patch -> patch review versions: +Python 3.3 -Python 2.7, Python 3.2 ___ Python tracker __

[issue7317] Display full tracebacks when an error occurs asynchronously

Julian added the comment: I wish there was a less instrusive of saying "+1. I'm happy. Thanks." than posting a whole comment, but until then: +1. I'm happy. Thanks. (I haven't inspected the code - just based on the description.) -- ___ Python trac

[issue7317] Display full tracebacks when an error occurs asynchronously

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue7317] Display full tracebacks when an error occurs asynchronously

alon horev added the comment: Here's the next attempt (took your advice about the convention): Exception ignored in: > Traceback (most recent call last): File "/tmp/bla.py", line 4, in __del__ None.someattr AttributeError: 'NoneType' object has no attribute 'someattr' reminder of the cur

[issue7317] Display full tracebacks when an error occurs asynchronously

Julian added the comment: The formatting isn't very conventional for Python. Why not use the normal format? i.e. Traceback (most recent call last): File "/tmp/bla.py", line 4, in __del__ None.someattr AttributeError: 'NoneType' object has no attribute 'someattr' Why is this more likely

[issue7317] Display full tracebacks when an error occurs asynchronously

alon horev added the comment: Submitting a patch proposing this format: -BEGIN UNRAISABLE EXCEPTION- Class: AttributeError Instance: "'NoneType' object has no attribute 'someattr'" Function: > Traceback (most recent call last): File "/tmp/bla.py", line 4, in __del__ None.someattr

[issue7317] Display full tracebacks when an error occurs asynchronously

Julian added the comment: Amaury asks: "Is there an already existing flag that could control this behaviour?" I wonder if the warnings module could be used. -- nosy: +oddthinking ___ Python tracker __

[issue7317] Display full tracebacks when an error occurs asynchronously

Amaury Forgeot d'Arc added the comment: Seconded. But such messages are also printed when the interpreter exits, when poorly written __del__ methods access already disposed modules. Raising a full traceback could cause users to think that the error is more severe than it is. Is there an alread

[issue7317] Display full tracebacks when an error occurs asynchronously

New submission from Antoine Pitrou : When an exception is raised in a __del__ method or a finalizer (i.e. a weakref callback), only the exception name is printed out. Unfortunately, arbitrarily complex code can be involved which makes debugging quite tedious. It would be nice to display the full