On Sun, Jul 13, 2008, Tom Mullins wrote: > > I do not know where cleanup_traceback (in run.py) is called, or really > anything about the inner workings of python, but there is a problem with > sys.tracebacklimit. If it is set to one or zero, "** IDLE Internal > Exception" is printed in the traceback for any exception, not internal ones. > I think tracebacklimit is applied to the traceback before cleanup_traceback > is called, but should be applied after. I imagine the solution is not that > simple, and you may already be aware of the problem, but thanks anyway. If you care about this issue, please file a report at bugs.python.org -- Aahz (aahz at pythoncraft.com) <*> http://www.pythoncraft.com/ I support the RKAB
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