[issue22135] allow to break into pdb with Ctrl-C for all the commands that resume execution

Change by Chun-Yu Tseng : -- pull_requests: +13175 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue22135] allow to break into pdb with Ctrl-C for all the commands that resume execution

Chun-Yu Tseng added the comment: My bad, I totally forget this patch. Need to spend some time to retest my code and catch up with current development flow. Thanks for reminding. -- ___ Python tracker __

[issue22135] allow to break into pdb with Ctrl-C for all the commands that resume execution

daniel hahler added the comment: Would be nice to have this indeed. Please consider creating a PR with an updated patch then for easier review. -- nosy: +blueyed ___ Python tracker __

[issue22135] allow to break into pdb with Ctrl-C for all the commands that resume execution

Xavier de Gaye added the comment: The code review of your first patch still applies to your last patch. -- ___ Python tracker ___ ___

[issue22135] allow to break into pdb with Ctrl-C for all the commands that resume execution

Chun-Yu Tseng added the comment: Ping :) -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue22135] allow to break into pdb with Ctrl-C for all the commands that resume execution

Chun-Yu Tseng added the comment: Appreciate for your quick response. I have already left the reply in Rietveld. I have uploaded a new patch with revised tests. In fact, the tests I wrote in the first patch are based on the style of `test_pdb2.py` in #7245 . But I am sure that now the new tests

[issue22135] allow to break into pdb with Ctrl-C for all the commands that resume execution

Xavier de Gaye added the comment: Thanks for the patch. See my comments in Rietveld. I think we can skip the 'step' command. For the tests, can you use the existing run_pdb() method and trigger the signals from within the code being executed with 'os.kill(os.getpid(), signal.SIGINT | signal.CT

[issue22135] allow to break into pdb with Ctrl-C for all the commands that resume execution

Chun-Yu Tseng added the comment: Here comes the patch: 1. Let Pdb can also resume from `return`, `until` and `next` commands when receiving Control-C. 2. Explicitly raise `bdb.BdbQuit` when an unexpected exception occurs in `sigint_handler`. See #24283. 3. Add two tests `test_break_during_in

[issue22135] allow to break into pdb with Ctrl-C for all the commands that resume execution

Changes by Xavier de Gaye : -- nosy: +georg.brandl ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue22135] allow to break into pdb with Ctrl-C for all the commands that resume execution

New submission from Xavier de Gaye: Pdb sets a handler for the SIGINT signal (which is sent when the user presses Ctrl-C on the console) when you give a continue command. 'continue' is not the only pdb command that may be interrupted, all the commands that resume the execution of the program (i