diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2010-07-25 21:35:21 -0400 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2010-07-25 21:35:21 -0400 |
| commit | 895b2d376d2dfe422d37a83f45f023c16be1f060 (patch) | |
| tree | bd7c915079e70c300021e526da3688706f36a3f1 /doc/excluding.rst | |
| parent | 93addb40491828011944fd8e352ce7fc2a50d4e9 (diff) | |
| download | python-coveragepy-git-895b2d376d2dfe422d37a83f45f023c16be1f060.tar.gz | |
Update the history timestamps.
Diffstat (limited to 'doc/excluding.rst')
| -rw-r--r-- | doc/excluding.rst | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/excluding.rst b/doc/excluding.rst index 55acebeb..466f56a7 100644 --- a/doc/excluding.rst +++ b/doc/excluding.rst @@ -6,6 +6,7 @@ Excluding code from coverage :history: 20090613T090500, brand new docs. :history: 20100224T200900, updated for 3.3. +:history: 20100725T211700, updated for 3.4. You may have code in your project that you know won't be executed, and you want @@ -91,3 +92,10 @@ Here's a list of exclusions I've used:: Note that when using the ``exclude_lines`` option in a configuration file, you are taking control of the entire list of regexes, so you need to re-specify the default "pragma: no cover" match if you still want it to apply. + + +Excluding source files +---------------------- + +See :ref:`source` for ways to limit what files coverage.py measures or reports +on. |
