Skip to content

Commit

Permalink
Clarify that capfdbinary captures on a filedescriptor level.
Browse files Browse the repository at this point in the history
The opening clause was the same for this paragraph and the previous paragraph, making it seem like they were duplicates. I added some text making it clearer that this paragraph is about filedescriptors.
  • Loading branch information
pradeep90 authored and nicoddemus committed Sep 25, 2024
1 parent fda1bbd commit 202d908
Showing 1 changed file with 3 additions and 4 deletions.
7 changes: 3 additions & 4 deletions doc/en/how-to/capture-stdout-stderr.rst
Original file line number Diff line number Diff line change
Expand Up @@ -149,10 +149,9 @@ the ``readouterr`` method.



If the code under test writes non-textual data, you can capture this using
the ``capfdbinary`` fixture which instead returns ``bytes`` from
the ``readouterr`` method. The ``capfdbinary`` fixture operates on the
filedescriptor level.
If the code under test writes non-textual data on a filedescriptor level, you
can capture this using the ``capfdbinary`` fixture which instead returns
``bytes`` from the ``readouterr`` method.



Expand Down

0 comments on commit 202d908

Please sign in to comment.