Upgrade to coverage 3.7.1 and have it auto-build itself on first use.

third_party/coverage-3.7.1/doc/faq.rst

 .. _faq:
 
 ==================
 FAQ and other help
 ==================
 
 :history: 20090613T141800, brand new docs.
 :history: 20091005T073900, updated for 3.1.
 :history: 20091127T201500, updated for 3.2.
 :history: 20110605T175500, add the announcement mailing list.
 :history: 20121231T104700, Tweak the py3 text.
 
 
 Frequently asked questions
 --------------------------
 
 **Q: I use nose to run my tests, and its cover plugin doesn't let me create
 HTML or XML reports.  What should I do?**
 
 First run your tests and collect coverage data with `nose`_ and its plugin.
 This will write coverage data into a .coverage file.  Then run coverage.py from
 the :ref:`command line <cmd>` to create the reports you need from that data.
 
 .. _nose: http://somethingaboutorange.com/mrl/projects/nose
 
 
 **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
 default.  Switch to the ``coverage run`` command, or use the ``-e`` switch to
 erase all data before starting the next run.
 
 
 **Q: Why do the bodies of functions (or classes) show as executed, but the def
 lines do not?**
 
@@ skipping 49 matching lines @@
 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
 `coveragepy-announce`_ mailing list.
 
 .. _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
 
 
 History
 -------
 
 Coverage.py was originally written by `Gareth Rees`_.
 Since 2004, `Ned Batchelder`_ has extended and maintained it with the help of
 `many others`_.  The :ref:`change history <changes>` has all the details.
 
 .. _Gareth Rees:    http://garethrees.org/
 .. _Ned Batchelder: http://nedbatchelder.com
 .. _many others:    http://bitbucket.org/ned/coveragepy/src/tip/AUTHORS.txt