diff options
author | Ned Batchelder <ned@nedbatchelder.com> | 2014-11-29 11:06:41 -0500 |
---|---|---|
committer | Ned Batchelder <ned@nedbatchelder.com> | 2014-11-29 11:06:41 -0500 |
commit | ad339d46c23f561d771d839ac2c32dc59a6c2254 (patch) | |
tree | 367ffa6e6cc4039f819a26c6e3f217367c0ace14 /doc/subprocess.rst | |
parent | 494fd347a542ab94112350da49bc91b8b1076578 (diff) | |
download | python-coveragepy-git-ad339d46c23f561d771d839ac2c32dc59a6c2254.tar.gz |
Fix spelling errors in the docs.
Diffstat (limited to 'doc/subprocess.rst')
-rw-r--r-- | doc/subprocess.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/subprocess.rst b/doc/subprocess.rst index 40875f7f..89d241c6 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 invokved. +coverage 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 @@ -69,5 +69,5 @@ write it. Note that if you use one of these techniques, you must undo them if you uninstall coverage.py, since you will be trying to import it during Python -startup. Be sure to remove the change when you uninstall coverage.py, or use a -more defensive approach to importing it. +start-up. Be sure to remove the change when you uninstall coverage.py, or use +a more defensive approach to importing it. |