Cheryl Sabella <cheryl.sabe...@gmail.com> added the comment:
I agree with Karthikeyan. If it's added to the pdb doc page, I think the existing text should stay as it is, but a 'New in 3.7' added after it. Something like: The typical usage to break into the debugger from a running program is to insert import pdb; pdb.set_trace() at the location you want to break into the debugger. You can then step through the code following this statement, and continue running without the debugger using the continue command. New in version 3.7: The built-in :func:`breakpoint()`, when called with defaults, can be used instead of ``import pdb; pdb.set_trace()``. ---------- nosy: +cheryl.sabella _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue35835> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
