This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients Tadhg McDonald-Jensen, kbk, roger.serwy, terry.reedy
Date 2016-03-25.22:24:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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 lines were here until I read this (3.5.2,, 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 = ['', '', '']
    for name in ('', '', ''):
        exclude.append(os.path.join('idlelib', name))
Date User Action Args
2016-03-25 22:24:37terry.reedysetrecipients: + terry.reedy, kbk, roger.serwy, Tadhg McDonald-Jensen
2016-03-25 22:24:37terry.reedysetmessageid: <>
2016-03-25 22:24:37terry.reedylinkissue26627 messages
2016-03-25 22:24:37terry.reedycreate