[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.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7317 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 tracker rep...@bugs.python.org http://bugs.python.org/issue7317 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 rep...@bugs.python.org http://bugs.python.org/issue7317 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7317] Display full tracebacks when an error occurs asynchronously
Changes by Martin Panter vadmium...@gmail.com: -- nosy: +vadmium ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7317 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7317] Display full tracebacks when an error occurs asynchronously
Changes by Andrew Svetlov andrew.svet...@gmail.com: -- nosy: +asvetlov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7317 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 rep...@bugs.python.org http://bugs.python.org/issue7317 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 rep...@bugs.python.org http://bugs.python.org/issue7317 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 rep...@bugs.python.org http://bugs.python.org/issue7317 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7317] Display full tracebacks when an error occurs asynchronously
Changes by Antoine Pitrou pit...@free.fr: -- Removed message: http://bugs.python.org/msg167273 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7317 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7317] Display full tracebacks when an error occurs asynchronously
alon horev alo...@gmail.com added the comment: how does one get his patch reviewed? (it's been 6 months) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7317 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7317] Display full tracebacks when an error occurs asynchronously
Changes by Éric Araujo mer...@netwok.org: -- keywords: +needs review priority: high - normal stage: needs patch - patch review versions: +Python 3.3 -Python 2.7, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7317 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7317] Display full tracebacks when an error occurs asynchronously
alon horev alo...@gmail.com added the comment: Submitting a patch proposing this format: -BEGIN UNRAISABLE EXCEPTION- Class: AttributeError Instance: 'NoneType' object has no attribute 'someattr' Function: bound method A.__del__ of __main__.A object at 0x1007671d0 Traceback (most recent call last): File /tmp/bla.py, line 4, in __del__ None.someattr -END UNRAISABLE EXCEPTION- I've wrapped the exception information with header/footer differentiating it from a user's error handling code that also prints tracebacks (is it too much?). I've considered using the warnings module, But I dislike the suppression of already warned messages. (2 instances will raise exception in __del__ but only one message will be printed) This is my first patch submission so feel free giving me a hard time. -- keywords: +patch nosy: +alonho Added file: http://bugs.python.org/file23413/7317.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7317 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7317] Display full tracebacks when an error occurs asynchronously
Julian python_...@somethinkodd.com 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 to get confused with user input than other unhandled exceptions? If you ARE going to deviate, it may be helpful to have it explain why this exception wasn't caught through the normal channels. Maybe the last line could be: Failed to raise this exception in __del__/finalizer method. or similar. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7317 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7317] Display full tracebacks when an error occurs asynchronously
alon horev alo...@gmail.com added the comment: Here's the next attempt (took your advice about the convention): Exception ignored in: bound method A.__del__ of __main__.A object at 0x1007671d0 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 current format for comparison: Exception AttributeError: 'NoneType' object has no attribute 'someattr' in bound method A.__del__ of __main__.A object at 0x1007671d0 ignored I thought about a more elaborate explanation than Exception ignored but grepping this function through the code shows it can be called from various places making it too generic. The reason I wanted to add a header/footer is for stating the message and the traceback go together (I print tracebacks to screen all the time), but it might be TMI.. -- Added file: http://bugs.python.org/file23414/7317.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7317 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7317] Display full tracebacks when an error occurs asynchronously
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7317 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7317] Display full tracebacks when an error occurs asynchronously
Julian python_...@somethinkodd.com 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 tracker rep...@bugs.python.org http://bugs.python.org/issue7317 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7317] Display full tracebacks when an error occurs asynchronously
Julian python_...@somethinkodd.com 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 rep...@bugs.python.org http://bugs.python.org/issue7317 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7317] Display full tracebacks when an error occurs asynchronously
Amaury Forgeot d'Arc amaur...@gmail.com 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 already existing flag that could control this behaviour? Otherwise, well, just ignore my remark. -- nosy: +amaury.forgeotdarc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7317 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7317] Display full tracebacks when an error occurs asynchronously
New submission from Antoine Pitrou pit...@free.fr: 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 traceback so that these errors are easier to diagnose (see issue7060 as an example). -- components: Interpreter Core, Library (Lib) messages: 95197 nosy: pitrou priority: high severity: normal stage: needs patch status: open title: Display full tracebacks when an error occurs asynchronously type: feature request versions: Python 2.7, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7317 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
