Skip to content

Commit

Permalink
Update docs/source/developer_guide/generator-runner.rst
Browse files Browse the repository at this point in the history
Co-authored-by: Adina Wagner <[email protected]>
  • Loading branch information
christian-monch and adswa authored Oct 20, 2023
1 parent bbdf2a4 commit 3429099
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/source/developer_guide/generator-runner.rst
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ The output of the subprocess is passed to an instance of a `protocol`-class in t

When the subprocess is executed the runner will invoke the appropriate callbacks.

``datalad_next`` provides some pre-defined protocol-classes for common use cases, e.g. ``datalad_next.runners.StdOutErrCapture``, which executes a subprocess and returns a dictionary with the ``stdout``- and ``stderr``-output, and the `return code` (also referred to as `exit status` ) of the subprocess.
``datalad_next`` provides some pre-defined protocol-classes for common use cases, e.g. ``datalad_next.runners.StdOutErrCapture``, which executes a subprocess and returns a dictionary with the ``stdout``- and ``stderr``-output, and the `return code` (also referred to as `exit status`) of the subprocess.
You are not limited to the existing protocol-classes.
Instead you may implement your own protocol-classes that could implement arbitrary operation, e.g. calculate a letter-histogram, trace response times, send all output to a file, or send all output to another process.

Expand Down

0 comments on commit 3429099

Please sign in to comment.