diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2013-09-17 20:15:53 -0400 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2013-09-17 20:15:53 -0400 |
| commit | a73c2b9bfe6679423cc8e1e8f83538a1caa030b4 (patch) | |
| tree | f8df74c332d4b3c068bd493c5a4c1a3f5561b65c /doc/faq.rst | |
| parent | a5d67a849961b4d16ef72f08e3ebb7ddf7d96de8 (diff) | |
| download | python-coveragepy-git-a73c2b9bfe6679423cc8e1e8f83538a1caa030b4.tar.gz | |
Remove notes about me being available for custom work, and rewrap many paragraphs.
Diffstat (limited to 'doc/faq.rst')
| -rw-r--r-- | doc/faq.rst | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/doc/faq.rst b/doc/faq.rst index 6b0c4af6..78db591f 100644 --- a/doc/faq.rst +++ b/doc/faq.rst @@ -26,9 +26,9 @@ the :ref:`command line <cmd>` to create the reports you need from that data. **Q: Why do unexecutable lines show up as executed?** -Usually this is because you've updated your code and run coverage on it -again without erasing the old data. Coverage records line numbers executed, so -the old data may have recorded a line number which has since moved, causing +Usually this is because you've updated your code and run coverage on it again +without erasing the old data. Coverage records line numbers executed, so the +old data may have recorded a line number which has since moved, causing coverage to claim a line has been executed which cannot be. If you are using the ``-x`` command line action, it doesn't erase first by @@ -98,8 +98,7 @@ Announcements of new coverage.py releases are sent to the .. _coveragepy-announce: http://groups.google.com/group/coveragepy-announce `I can be reached`__ in a number of ways, I'm happy to answer questions about -using coverage.py. I'm also available hourly for consultation or custom -development. +using coverage.py. __ http://nedbatchelder.com/site/aboutned.html |