Terry J. Reedy added the comment:
The goal is to match the traceback that Python itself produces with the same
code, but it is perhaps an impossible process. The current list goes back to
2003 without tracker issue numbers, so I don't know the reason for each. I
worry a bit about the suppression of lines from threading and queue.
I wondered why the idlelib.run lines were here until I read this (3.5.2,
run.py, line 233-236.
if len(tb) == 0:
# exception was in IDLE internals, don't prune!
tb[:] = orig_tb[:]
print("** IDLE Internal Exception: ", file=sys.stderr)
So both lines were deleted and then restored.
Prepending idlelib as appropriate, seems like a good idea.
exclude = ['bdb.py', 'queue.py', 'threading.py']
for name in ('RemoteDebugger.py', 'rpc.py', 'run.py'):
exclude.append(os.path.join('idlelib', name))
----------
stage: -> test needed
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26627>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
