bpo-35835: Add reference to Python 3.7 new breakpoint() function in pdb documentation. (GH-11691)
https://github.com/python/cpython/commit/7516f265a8517e4fdc7d6e63d72ae1b57fd... commit: 7516f265a8517e4fdc7d6e63d72ae1b57fda26ee branch: 3.7 author: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> committer: GitHub <noreply@github.com> date: 2019-01-30T09:41:51-08:00 summary: 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> files: M Doc/library/pdb.rst diff --git a/Doc/library/pdb.rst b/Doc/library/pdb.rst index a72876f3f5a8..c7864e9e3f22 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
participants (1)
-
Miss Islington (bot)