Michael Glassford wrote: > In Python 2.4, traceback.print_exc() and traceback.format_exc() silently > do nothing if there is no active exception; in Python 2.5, they raise an > exception. Not too difficult to handle, but unexpected (and a pain if > you use it in a lot of places). I assume it was an unintentional change?
This was certainly an unintentional change while restructuring some internal traceback routines. It's now fixed in SVN. Georg _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
