We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
Originally reported by: Lutz Prechelt (BitBucket: prechelt, GitHub: prechelt)
I see that it might be useful to be able to suppress output reporting when using readouterr(). But that this happens automatically and there is no obvious way to turn reporting back on is both surprising and, I think, inconvenient. See a detailed description here: http://stackoverflow.com/questions/26561822/pytest-capsys-checking-output-and-getting-it-reported
The text was updated successfully, but these errors were encountered:
I think this is working as designed, and it can be disabled temporarily with the capsys.disabled() context manager. 👍
capsys.disabled()
Sorry, something went wrong.
No branches or pull requests
Originally reported by: Lutz Prechelt (BitBucket: prechelt, GitHub: prechelt)
I see that it might be useful to be able to suppress output reporting when using readouterr().
But that this happens automatically and there is no obvious way to turn reporting back on is both surprising and, I think, inconvenient.
See a detailed description here:
http://stackoverflow.com/questions/26561822/pytest-capsys-checking-output-and-getting-it-reported
The text was updated successfully, but these errors were encountered: