Python 3.14: Ctrl+D behavior during debugging

[nicoddemus]

As discussed in this GitHub comment, pressing Ctrl+D in the debugger now quits the entire test session, whereas previously, it only failed the current test.

We need to decide how to proceed:

1. Implement consistent behavior across all versions. If so, which behavior should we choose?
2. Keep the behavior different -- this may not be a major issue since it's an interactive feature.

[nicoddemus]

Personally, I'm fine with option 2 (keeping different behaviors). However, if others prefer Option 1 (enforcing consistency), I'd favor quitting the entire test session rather than just failing the current test.

[RonnyPfannschmidt]

Unless we get a way to continue a testrun, I'd prefer that exiting the debugger simply continues the run

[jakkdl]

Unless we get a way to continue a testrun, I'd prefer that exiting the debugger simply continues the run

well, if you want to continue the run while at the pdb prompt you can do the command cont[inue]. The "additional" behavior that Ctrl+D gives currently is making the current test fail (because you inject BdbQuit) and it then continuing to run all other tests. Which seems like kind of a strange thing to want?

The counterargument is that you can exit the full test session by doing quit, so if that's what users want to do they should simply quit instead of Ctrl+D. Though I personally had no idea that's how it would work, and I'm used to the workflow of C+D for quitting from other apps, so for the longest time I've always paired --pdb with -x.

Keep the behavior different -- this may not be a major issue since it's an interactive feature.

I don't love this, every now and then I do tox -e pyXX -- --pdb and would like it if different versions behaved the same way.

[RonnyPfannschmidt]

Then lets turn the pdb exit into a fail + should stop in all cases