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 | d6a7a11f8c5a8e73a9dfd9a1ce602df775d04586 (patch) | |
| tree | 07700ed00c3a0d41013f466952cf0d1ebef7b810 /doc/subprocess.rst | |
| parent | a22d3cad02f5b0f2f76e5ef6b9f09d421ca99b76 (diff) | |
| download | python-coveragepy-d6a7a11f8c5a8e73a9dfd9a1ce602df775d04586.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 cce2c0b..92ad135 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 |
