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
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4