Xavier de Gaye added the comment:
Yes the patch does change the semantics of the quit command:
* no change when pdb is run as a script or with 'python -m pdb
script_name'. As stated in the doc, the 'quit command': "Quit from the
debugger. The program being executed is aborted."
* but when a set_trace() breakpoint is inserted, 'quit' just terminates the
debugger and the program continues its execution. It is the purpose of the
patch to prevent an inconvenient crash with BdbQuit in that case. The idea is
that the hard-coded breakpoint was set to investigate a local problem and one
may want to let it run afterwards (for example to check its behavior after
having changed some its internal state with pdb).
Sorry, I should have documented that behavior change.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue16446>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
