This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author cheryl.sabella
Recipients cheryl.sabella, docs@python, jcrmatos, xtreak
Date 2019-01-27.13:51:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1548597085.24.0.0326589091436.issue35835@roundup.psfhosted.org>
In-reply-to
Content
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()``.
History
Date User Action Args
2019-01-27 13:51:27cheryl.sabellasetrecipients: + cheryl.sabella, docs@python, jcrmatos, xtreak
2019-01-27 13:51:25cheryl.sabellasetmessageid: <1548597085.24.0.0326589091436.issue35835@roundup.psfhosted.org>
2019-01-27 13:51:25cheryl.sabellalinkissue35835 messages
2019-01-27 13:51:25cheryl.sabellacreate