capsys interferes with debugging

[pytestbot]

Originally reported by: BitBucket: amcnabb8, GitHub: amcnabb8

---

I used capsys to test the output of a function that prints to stdout. The function failed before the capsys.readouterr() line, and its output was essential to determining what went wrong. The FAILURES list in py.test did not contain any of the output. It seems that in this situation, py.test should print all of the captured output in the FAILURES list, as it would if capsys were not present.

The following paste shows a minimal example with and without capsys:

http://paste.pocoo.org/show/560459

Note that for test_nocap, "hi" appears in the "captured stdout", but for test_capsys, this information is unavailable. It seems to me that "hi" should be shown for both cases.

Thanks for the work you put into pytest; it's a great project.

---

• Bitbucket: https://bitbucket.org/pytest-dev/pytest/issue/128

[pytestbot]

Original comment by Ronny Pfannschmidt (BitBucket: RonnyPfannschmidt, GitHub: RonnyPfannschmidt):

---

this needs the introduction of a way to track sub-captures

there is need for discussion with holger for an good approach

currently capsys discards the output if you do not use it in the test

[pytestbot]

Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42):

---

fix issue128 - show captured output when capsys/capfd are in use

[pytestbot]

Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42):

---

you can try installation with "pip install -i http://pypi.testrun.org -U pytest", shoulkd give you 2.2.5.dev1