[issue21997] Pdb.set_trace debugging does not end correctly

R. David Murray added the comment: Your point being? :) What needs to happen is for someone to review the issue and figure out if there is anything left to do. Has termination been fixed? Has the test case mentioned in the last message been incorporated? -- nosy: +r.david.murray

[issue21997] Pdb.set_trace debugging does not end correctly

ppperry added the comment: This issue seems to have languished for over two years. -- nosy: +ppperry ___ Python tracker ___ ___ Python

[issue21997] Pdb.set_trace debugging does not end correctly

Xavier de Gaye added the comment: > # This returns to a '>>>' prompt, At the above line in Terry test, the debugger is not terminated and on linux when I type at this point I get: >>> --Call-- > /home/xavier/etc/.pystartup(21)save_history() -> def save_history(historyPath=historyPath): (Pdb)

[issue21997] Pdb.set_trace debugging does not end correctly

Terry J. Reedy added the comment: With Python 3.4.1, Win 7, there is a detour stepping through displayhook before arriving at the same place with the same result upon quitting. If one does not quit, stepping ends at > c:\programs\python34\lib\threading.py(235)__enter__() -> return self._lock._

[issue21997] Pdb.set_trace debugging does not end correctly in IDLE

Xavier de Gaye added the comment: Two issues here: a) in IDLE, on a 'return' debug event in the main module, the step command does not end the debugging session. b) in IDLE, BdbQuit is raised by the quit command when the debugger is started with pdb.set_trace(). I do not know IDLE, but a) seem

[issue21997] Pdb.set_trace debugging does not end correctly in IDLE

Changes by ppperry : -- hgrepos: -264 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/

[issue21997] Pdb.set_trace debugging does not end correctly in IDLE

Changes by ppperry : -- hgrepos: +264 nosy: +georg.brandl, terry.reedy -ppperry ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue21997] Pdb.set_trace debugging does not end correctly in IDLE

Changes by ppperry : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue21997] Pdb.set_trace debugging does not end correctly in IDLE

New submission from ppperry: In IDLE: >>>def dodebug(): pdb.set_trace() >>>dodebug() --Return-- > (2)dodebug()->None (Pdb) s --Return-- > (1)()->None (Pdb) s PDB should exit, but it doesn't > c:\python27\lib\idlelib\run.py(308)runcode() -> interruptable =