You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the SimpleTestResourceWrapper uses with self._debugging_output.capture_stdout_and_stderr() to capture stdout and stderr with no way to disable it. This prevents using pdb for test debugging because it's unable to pipe stdout/stderr. I have manually patched my sources by adding a capture: bool = False option in each of the resource hook functions, but it would be nice to have it supported with your intentional design input.
I could also fork and submit a PR, if needed.
The text was updated successfully, but these errors were encountered:
Hi @riebecj, thank you for raising this, and for the detailed description.
The TestResourceWrapper subclasses are due an overhaul at some point in the future, but in the meantime I'd be happy for you to take a crack at fixing this specific issue, as it is definitely not the behaviour we want.
If you're able to hook it into TestResourceWrapper.capture_debugging to properly toggle the capturing in a way that works with pdb then that would be ideal, although I appreciate it might be difficult to change with the current implementation. Either way we'd welcome a PR.
Currently, the
SimpleTestResourceWrapper
useswith self._debugging_output.capture_stdout_and_stderr()
to capture stdout and stderr with no way to disable it. This prevents usingpdb
for test debugging because it's unable to pipe stdout/stderr. I have manually patched my sources by adding acapture: bool = False
option in each of the resource hook functions, but it would be nice to have it supported with your intentional design input.I could also fork and submit a PR, if needed.
The text was updated successfully, but these errors were encountered: