Skip to content

Conversation

blueyed
Copy link
Collaborator

@blueyed blueyed commented Apr 30, 2019

This is required for when the UnixConsole instance was created with
stdin being a terminal, but then later not so anymore.

E.g. having used pdbpp before pytest captures output, and then having a
set_trace where pytest is capturing output, but the debugging plugin
(which suspends capturing) is not active yet (pytest_load_initial_conftests).

This will result in pdb raising BdbQuit then "correctly".

@blueyed
Copy link
Collaborator Author

blueyed commented Apr 30, 2019

Slightly related pytest issue pytest-dev/pytest#5189.

blueyed added 3 commits April 11, 2021 12:19
This is required for when the UnixConsole instance was created with
stdin being a terminal, but then later not so anymore.

E.g. having used pdbpp before pytest captures output
(`pdb.set_trace()`), and then continuing (`c`).
pytest is capturing output by now then, but the debugging plugin (which
suspends capturing) might not be active yet (pytest_load_initial_conftests).

This patch makes it raise `BdbQuit` then "correctly".
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant