diff options
author | Ned Batchelder <ned@nedbatchelder.com> | 2015-07-23 21:22:30 -0400 |
---|---|---|
committer | Ned Batchelder <ned@nedbatchelder.com> | 2015-07-23 21:22:30 -0400 |
commit | 080e181a8cc21b8e555fa96eaa54762eb2a76c8e (patch) | |
tree | 2b60605f7b2d8d57255039d718d238ce4cb0c493 /doc/subprocess.rst | |
parent | c7d226aa8ba7c8c37fdda5f594b1fff6f073a872 (diff) | |
download | python-coveragepy-git-080e181a8cc21b8e555fa96eaa54762eb2a76c8e.tar.gz |
Refer to the project consistenly as coverage.py. #275
Diffstat (limited to 'doc/subprocess.rst')
-rw-r--r-- | doc/subprocess.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/subprocess.rst b/doc/subprocess.rst index cce2c0bf..92ad135a 100644 --- a/doc/subprocess.rst +++ b/doc/subprocess.rst @@ -30,7 +30,7 @@ Measuring coverage in sub-processes is a little tricky. When you spawn a sub-process, you are invoking Python to run your program. Usually, to get coverage measurement, you have to use coverage.py to run your program. Your sub-process won't be using coverage.py, so we have to convince Python to use -coverage even when not explicitly invoked. +coverage.py even when not explicitly invoked. To do that, we'll configure Python to run a little coverage.py code when it starts. That code will look for an environment variable that tells it to start |