summaryrefslogtreecommitdiff
path: root/Doc
diff options
context:
space:
mode:
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>2019-01-30 09:41:51 -0800
committerGitHub <noreply@github.com>2019-01-30 09:41:51 -0800
commit7516f265a8517e4fdc7d6e63d72ae1b57fda26ee (patch)
treeeba5dbd82d214414f9569024393e547b4c165d16 /Doc
parent1c79891026c57046f5ac596080ea60c515e0560a (diff)
downloadcpython-git-7516f265a8517e4fdc7d6e63d72ae1b57fda26ee.tar.gz
bpo-35835: Add reference to Python 3.7 new breakpoint() function in pdb documentation. (GH-11691)
(cherry picked from commit cf991e653ac550a9f011631447c61ce583404a57) Co-authored-by: João Matos <jcrmatos@gmail.com>
Diffstat (limited to 'Doc')
-rw-r--r--Doc/library/pdb.rst4
1 files changed, 4 insertions, 0 deletions
diff --git a/Doc/library/pdb.rst b/Doc/library/pdb.rst
index a72876f3f5..c7864e9e3f 100644
--- a/Doc/library/pdb.rst
+++ b/Doc/library/pdb.rst
@@ -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