| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead. |
Sorry, something went wrong.
Co-authored-by: Tian Gao <gaogaotiantian@hotmail.com>
…MJD4Y.rst Co-authored-by: Tian Gao <gaogaotiantian@hotmail.com>
|
Thank you for the PR! |
Sorry, something went wrong.
|
Thanks for the merge! And thanks for being super responsive and all your hard work on pdb! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This change should mean it's again possible to call breakpoint() in a REPL session and return to the REPL session with q/quit/exit/EOF.
The test has a slight workaround/hack because I couldn't figure out how to call breakpoint() and simulate using pdb interactively within a simulated REPL session in a subprocess. After set_trace() was called, pdb would receive an EOF and exit before it could receive further commands.
If there's interest, I could also add the code from PR129768 to shorten the BdbQuit traceback by one frame.