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
In trying to move to click's new support for not mixing stdout and stderr, I encountered that click misinterprets an empty stderr as not having asked to not mix stdout and stderr.
https://github.com/pallets/click/blob/20a2bd8a13/click/testing.py#L105-L106 looks like the offending lines.
Failing test case:
import click from click.testing import CliRunner @click.command() def cli_empty_stderr(): click.echo("stdout") runner = CliRunner(mix_stderr=False) result = runner.invoke(cli_empty_stderr) assert result.output == 'stdout\n' assert result.stdout == 'stdout\n' assert result.stderr == ''
The text was updated successfully, but these errors were encountered:
Don't claim empty stderrs weren't separately captured.
510fd0c
Closes: pallets#1193.
6bcdc1e
ba5fc39
f698211
No branches or pull requests
In trying to move to click's new support for not mixing stdout and stderr, I encountered that click misinterprets an empty stderr as not having asked to not mix stdout and stderr.
https://github.com/pallets/click/blob/20a2bd8a13/click/testing.py#L105-L106 looks like the offending lines.
Failing test case:
The text was updated successfully, but these errors were encountered: