Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

bpo-35835: Add reference to Python 3.7 new breakpoint() function in pdb documentation. #11691

Merged
merged 3 commits into from
Jan 30, 2019
Merged

bpo-35835: Add reference to Python 3.7 new breakpoint() function in pdb documentation. #11691

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e425115
Add reference to Python 3.7 new breakpoint() function.
jcrmatos Jan 28, 2019
eff06f5
Comply with max line length.
Mariatta Jan 28, 2019
18082c1
Remove trailing white space.
jcrmatos Jan 28, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions Doc/library/pdb.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,10 @@ 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 :pdbcmd:`continue` command.

.. versionadded:: 3.7
The built-in :func:`breakpoint()`, when called with defaults, can be used
instead of ``import pdb; pdb.set_trace()``.

The typical usage to inspect a crashed program is::

>>> import pdb
Expand Down