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
This makes it difficult to distinguish between standard output and error messages. This makes things partically tricky when working with structured outputs (say, JSON), where warnings that can be ignored are printed to standard error. Merged output can't be decoded and it's challenging to filter-out warning messages.
Would it be possible to modify the execute function, to return stdout and stderr separately, or provide an option to keep them distinct? This would greatly improve usability when handling container output.
The text was updated successfully, but these errors were encountered:
rabbull
changed the title
[Feature Request] Separate stderr from stdout in execute function
Feature Request: Separate stderr from stdout in execute function
Feb 4, 2025
Thanks for your work on this project! It's incredibly useful!
However, I noticed that the
execute
function merges thestderr
output of the container intostdout
.pytest-docker/src/pytest_docker/plugin.py
Line 27 in d8939c8
This makes it difficult to distinguish between standard output and error messages. This makes things partically tricky when working with structured outputs (say, JSON), where warnings that can be ignored are printed to standard error. Merged output can't be decoded and it's challenging to filter-out warning messages.
Would it be possible to modify the
execute
function, to returnstdout
andstderr
separately, or provide an option to keep them distinct? This would greatly improve usability when handling container output.The text was updated successfully, but these errors were encountered: