diff options
| -rw-r--r-- | coverage/htmlfiles/index.html | 4 | ||||
| -rw-r--r-- | doc/branch.rst | 6 | ||||
| -rw-r--r-- | doc/faq.rst | 2 |
3 files changed, 6 insertions, 6 deletions
diff --git a/coverage/htmlfiles/index.html b/coverage/htmlfiles/index.html index 16f55180..04b314a3 100644 --- a/coverage/htmlfiles/index.html +++ b/coverage/htmlfiles/index.html @@ -33,8 +33,8 @@ <span class='key'>m</span> <span class='key'>x</span> {% if arcs %} - <span class='key'>b</span> - <span class='key'>p</span> + <span class='key'>b</span> + <span class='key'>p</span> {% endif %} <span class='key'>c</span> change column sorting </p> diff --git a/doc/branch.rst b/doc/branch.rst index 40e0a066..d9b61629 100644 --- a/doc/branch.rst +++ b/doc/branch.rst @@ -103,9 +103,9 @@ Here the while loop will never exit normally, so it doesn't take both of its "if 0:", coverage.py understands what is going on. In these cases, the line will not be marked as a partial branch. -But there are many ways in your own code to write intentionally partial +But there are many ways in your own code to write intentionally partial branches, and you don't want coverage.py pestering you about them. You can -tell coverage.py that you don't want them flagged by marking them with a +tell coverage.py that you don't want them flagged by marking them with a pragma:: i = 0 @@ -114,7 +114,7 @@ pragma:: break Here the while loop will never complete because the break will always be taken -at some point. Coverage.py can't work that out on its own, but the +at some point. Coverage.py can't work that out on its own, but the "no partial" pragma indicates that the branch is known to be partial, and the line is not flagged. diff --git a/doc/faq.rst b/doc/faq.rst index d495721d..ef27c291 100644 --- a/doc/faq.rst +++ b/doc/faq.rst @@ -91,7 +91,7 @@ Bug reports are gladly accepted at the `Bitbucket issue tracker`_. .. _Bitbucket issue tracker: http://bitbucket.org/ned/coveragepy/issues -Announcements of new coverage.py releases are sent to the +Announcements of new coverage.py releases are sent to the `coveragepy-announce`_ mailing list. .. _coveragepy-announce: http://groups.google.com/group/coveragepy-announce |