> In any case, I think there's room for providing more information in > the traceback than there is now, even without decompiling > anything. For example, I'd like to see some indication of the values > (or at least the types) being passed to each function call. In many > cases, that would save me a trip around the insert_print_statements- > run-fix_the_bug-take_the_print_ statements_out_again loop. Check out cgitb.py. It does a lot of that (albeit in HTML). --Guido van Rossum (home page: http://www.python.org/~guido/)
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