summaryrefslogtreecommitdiff
path: root/doc/subprocess.rst
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2010-11-05 17:27:33 -0400
committerNed Batchelder <ned@nedbatchelder.com>2010-11-05 17:27:33 -0400
commitc112ad01ff51bd5a7e9b85fd27644c18463b1698 (patch)
tree0818a538da3e5d15bbd9182002f7931d2c72fa76 /doc/subprocess.rst
parentdb0260bfeb86893cd03b93ccab288dce24262591 (diff)
downloadpython-coveragepy-c112ad01ff51bd5a7e9b85fd27644c18463b1698.tar.gz
Trim whitespace
Diffstat (limited to 'doc/subprocess.rst')
-rw-r--r--doc/subprocess.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/subprocess.rst b/doc/subprocess.rst
index bcf5044..9e223d8 100644
--- a/doc/subprocess.rst
+++ b/doc/subprocess.rst
@@ -28,7 +28,7 @@ Configuring Python for subprocess coverage
To measure coverage in subprocesses, you have to do two things: set a value for
the ``COVERAGE_PROCESS_START`` environment variable, and then invoke
-:func:`coverage.process_startup`.
+:func:`coverage.process_startup`.
How you set ``COVERAGE_PROCESS_START`` depends on the details of how you create
subprocesses. As long as the environment variable is visible in your subprocess,