Antoine Pitrou <pit...@free.fr> added the comment: > During handling of the above exception, another exception occurred: > > This is a blatant falsehood -- another exception did not occur, a > different exception was raised.
This doesn't make any difference in any other context, so why would it here? If only the above sentence is problematic, you can perhaps suggest another one. > Now, when another exception does actually occur, I'm all for the > nested traceback, but if I'm raising a different one, why is this > useful: To me that's the same as asking why the full call stack is useful. In some cases it is useful, in other cases it is distracting. Python displays comprehensive information by default. As I said, this can be tweaked using the traceback module. By the way, this is all described in detail in a PEP: http://www.python.org/dev/peps/pep-3134/ ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6210> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
