[issue24252] IDLE removes elements from tracebacks.

Change by Terry J. Reedy : -- versions: +Python 3.10 -Python 3.6, Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue24252] IDLE removes elements from tracebacks.

Terry J. Reedy added the comment: #26627 was closed as an apparent duplicate of this. It should be rechecked if this is fixed. -- assignee: -> terry.reedy versions: +Python 3.7 -Python 2.7, Python 3.4, Python 3.5 ___ Python tracker

[issue24252] IDLE removes elements from tracebacks.

ppperry added the comment: Your proposed patch does not work in its current form on my IDLE, but it does if I change tr[0][:-6] to tr[0][-6:] in the pdb checking code. Additionally, my proposed cleanup function did distinguish the difference between the unix and windows directory seperators

[issue24252] IDLE removes elements from tracebacks.

ppperry added the comment: I mean if someone starts a new copy of idle from within the IDLE python shell itself by The only situation that this function would behave wrongly is when someone launches IDLE from the shell (Why would they do that?). --

[issue24252] IDLE removes elements from tracebacks.

Terry J. Reedy added the comment: Did you test my proposed patch? I am reluctant to make major changes in the absence of either documentation for why the code is as it is or test cases. So I do not know about trimming top versus bottom and the examples intended to show both are needed. I

[issue24252] IDLE removes elements from tracebacks.

ppperry added the comment: Another example of this overzealous removing is when you create a module named rpc, run, RemoteDebugger, or bdb. For example (in this environment, a file in the current directory named rpc.py exists and refers to the undefined name bar): import rpc Traceback (most

[issue24252] IDLE removes elements from tracebacks.

ppperry added the comment: Is there any reason why the end of the traceback, rather then just the beginning, needs to be pruned in the first place? Additionally, the search for pdb in the tb method will still undesirably prune the traceback if someone invents there own buggy debugger that

[issue24252] IDLE removes elements from tracebacks.

Terry J. Reedy added the comment: Your message arrived as I was just starting on this issue, wondering whether the exclusion of threading and queue blocks is proper and wishing for an easy test example, such as you provided. It verifies the issue in 3.x. It also answers the question:

[issue24252] IDLE removes elements from tracebacks.

ppperry added the comment: This problem also occurs in other situati, such as when trying to get items from an empty queue import Queue Q = Queue.Queue() q.get_nowait() Traceback (most recent call last): File pyshell#16, line 1, in module q.get_nowait() Empty In that case, it doesn't

[issue24252] IDLE removes elements from tracebacks.

Terry J. Reedy added the comment: The two additional entries are the last two. In this case, they are needed because KeyError pertains to the dict lookup in the last line self.breaks[filename]. Mistaken in this particular case or not, the deletion is intentional. Run.print_exception has

[issue24252] IDLE removes elements from tracebacks.

New submission from ppperry: When reproducing issue24160 in IDLE, I saw this traceback: Traceback (most recent call last): File pyshell#14, line 1, in module pdb.run(reload(test3)) File C:\Python27\lib\pdb.py, line 1238, in run Pdb().run(statement, globals, locals) File