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

third_party/coverage-3.7.1/doc/index.rst

 ===========
 coverage.py
 ===========
 
 :history: 20090524T134300, brand new docs.
 :history: 20090613T164000, final touches for 3.0
 :history: 20090618T195900, minor tweaks
 :history: 20090707T205200, changes for 3.0.1
 :history: 20090913T084400, new command line syntax
 :history: 20091004T211900, version 3.1
@@ skipping 11 matching lines @@
 :history: 20110827T221800, update for 3.5.1b1
 :history: 20110923T081800, update for 3.5.1
 :history: 20120429T162100, updated for 3.5.2b1
 :history: 20120503T233800, updated for 3.5.2
 :history: 20120929T093500, updated for 3.5.3
 :history: 20121117T094900, Change from easy_install to pip.
 :history: 20121128T203700, Updated for 3.6b1.
 :history: 20121223T180600, Updated for 3.6b2.
 :history: 20121229T112300, Updated for 3.6b3.
 :history: 20130105T174000, Updated for 3.6
+:history: 20131005T210000, Updated for 3.7
+:history: 20131212T213300, Updated for 3.7.1
 
 
 Coverage.py is a tool for measuring code coverage of Python programs. It
 monitors your program, noting which parts of the code have been executed, then
 analyzes the source to identify code that could have been executed but was not.
 
 Coverage measurement is typically used to gauge the effectiveness of tests. It
 can show which parts of your code are being exercised by tests, and which are
 not.
 
 .. ifconfig:: not prerelease
 
-    The latest version is coverage.py 3.6, released 5 January 2013.
-    It is supported on Python versions 2.3 through 3.3, and PyPy 1.8.
+    The latest version is coverage.py 3.7.1, released 13 December 2013.
+    It is supported on Python versions 2.3 through 3.4, and PyPy 2.1.
 
 .. ifconfig:: prerelease
 
     The latest version is coverage.py 3.6b3, released 29 December 2012.
     It is supported on Python versions 2.3 through 3.3, and PyPy 1.9.
     **This is a pre-release build.  The usual warnings about possible bugs apply.**
     The latest stable version is coverage.py 3.5.3, `described here`_.
 
 .. _described here: http://nedbatchelder.com/code/coverage
 
@@ skipping 71 matching lines @@
 
 Getting help
 ------------
 
 If the :ref:`FAQ <faq>` doesn't answer your question, you can discuss
 coverage.py or get help using it on the `Testing In Python`_ mailing list.
 
 .. _Testing In Python: http://lists.idyll.org/listinfo/testing-in-python
 
 Bug reports are gladly accepted at the `Bitbucket issue tracker`_.
-Bitbucket also hosts the `code repository`_.
+Bitbucket also hosts the `code repository`_. There is a `mirrored repo`_ on
+Github.
 
 .. _Bitbucket issue tracker: http://bitbucket.org/ned/coveragepy/issues
 .. _code repository: http://bitbucket.org/ned/coveragepy
+.. _mirrored repo: https://github.com/nedbat/coveragepy
 
 `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.
 
 .. _I can be reached:  http://nedbatchelder.com/site/aboutned.html
 
 
 
 More information
 ----------------
 
 .. toctree::
     :maxdepth: 1
 
     install
     cmd
     config
     source
     excluding
     branch
     subprocess
     api
     contributing
     trouble
     faq
     changes
 
 
 .. How it works
 .. .coverage file format