[issue26627] IDLE incorrectly labeling error as internal

Changes by Terry J. Reedy : -- assignee: -> terry.reedy resolution: -> duplicate stage: test needed -> resolved status: open -> closed superseder: -> IDLE removes elements from tracebacks. ___ Python tracker

[issue26627] IDLE incorrectly labeling error as internal

ppperry added the comment: Duplicate issue24252, although the consequences are slightly different. -- nosy: +ppperry ___ Python tracker ___

[issue26627] IDLE incorrectly labeling error as internal

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

[issue26627] IDLE incorrectly labeling error as internal

Tadhg McDonald-Jensen added the comment: other then bdb.py all of the excluded modules are imported into idlelib.run so that line could be replaced with: import bdb exclude = (__file__, rpc.__file__, threading.__file__, queue.__file__, RemoteDebugger.__file__, bdb.__file__)

[issue26627] IDLE incorrectly labeling error as internal

Changes by Serhiy Storchaka : -- nosy: +kbk, roger.serwy, terry.reedy versions: +Python 3.6 ___ Python tracker ___

[issue26627] IDLE incorrectly labeling error as internal

New submission from Tadhg McDonald-Jensen: (I apologize if I'm doing something wrong) When using a file named run.py in idle, any errors raised from the module makes IDLE show a traceback like this: Traceback (most recent call last): ** IDLE Internal Exception: File