diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2011-06-04 21:26:33 -0400 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2011-06-04 21:26:33 -0400 |
| commit | 140c97e2a727243025d49f1da18eae979c6c2929 (patch) | |
| tree | bc5d40c3fcc592b54ddb7dacc8aec2724d02527d /doc/excluding.rst | |
| parent | 15addf22adbfd1070fbb88799a3f90b4e1da61d9 (diff) | |
| download | python-coveragepy-git-140c97e2a727243025d49f1da18eae979c6c2929.tar.gz | |
Update the docs for 3.5 changes.
Diffstat (limited to 'doc/excluding.rst')
| -rw-r--r-- | doc/excluding.rst | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/excluding.rst b/doc/excluding.rst index 466f56a7..9a3b5e7d 100644 --- a/doc/excluding.rst +++ b/doc/excluding.rst @@ -7,6 +7,7 @@ Excluding code from coverage :history: 20090613T090500, brand new docs. :history: 20100224T200900, updated for 3.3. :history: 20100725T211700, updated for 3.4. +:history: 20110604T184400, updated for 3.5. You may have code in your project that you know won't be executed, and you want @@ -76,7 +77,7 @@ all of them by adding a regex to the exclusion list:: [report] exclude_lines = def __repr__ -Here's a list of exclusions I've used:: +For example, here's a list of exclusions I've used:: [report] exclude_lines = @@ -93,6 +94,9 @@ 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. +A similar pragma, "no partial", can be used to tailor branch coverage +measurement. See :ref:`branch` for details. + Excluding source files ---------------------- |