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

third_party/coverage-3.7.1/doc/faq.rst

Index: third_party/coverage-3.7.1/doc/faq.rst
diff --git a/third_party/coverage-3.6/doc/faq.rst b/third_party/coverage-3.7.1/doc/faq.rst
similarity index 93%
rename from third_party/coverage-3.6/doc/faq.rst
rename to third_party/coverage-3.7.1/doc/faq.rst
index 6b0c4af6e77a0da2fa0da16ee90dadec91580de7..78db591f0d60dde635feaf13ad8b67bac4778b9a 100644
--- a/third_party/coverage-3.6/doc/faq.rst
+++ b/third_party/coverage-3.7.1/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