Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't eat stderr when subprocesses are run successfully #469

Open
marco-c opened this issue Mar 23, 2020 · 2 comments
Open

Don't eat stderr when subprocesses are run successfully #469

marco-c opened this issue Mar 23, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@marco-c
Copy link
Collaborator

marco-c commented Mar 23, 2020

There might be useful information anyway, so we shouldn't eat it in

def run_check(command, **kwargs):
.

@marco-c marco-c added the enhancement New feature or request label Mar 23, 2020
@anubhabsen
Copy link
Contributor

Would it be enough to return the error along with the output in the run_check() function and handle it in the other files where the function is called?

@marco-c
Copy link
Collaborator Author

marco-c commented May 18, 2020

I think we can just stop piping it (so it's redirected to the parent process' stderr).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants