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

third_party/coverage-3.7.1/doc/trouble.rst

Index: third_party/coverage-3.7.1/doc/trouble.rst
diff --git a/third_party/coverage-3.6/doc/trouble.rst b/third_party/coverage-3.7.1/doc/trouble.rst
similarity index 83%
rename from third_party/coverage-3.6/doc/trouble.rst
rename to third_party/coverage-3.7.1/doc/trouble.rst
index c7693c9e00eb62785ac90d076dbf68b61b0f9bea..f1c2cfbdc63f18d9fcfd2ccfbb2d5ff8dbd5cac4 100644
--- a/third_party/coverage-3.6/doc/trouble.rst
+++ b/third_party/coverage-3.7.1/doc/trouble.rst
@@ -11,9 +11,9 @@ there are some situations it can't cope with.  This page details some known
 problems, with possible courses of action, and links to coverage.py bug reports
 with more information.
 
-I would love to :ref:`hear from you <contact>` if you have information about any of
-these problems, even just to explain to me why you want them to start working
-properly.
+I would love to :ref:`hear from you <contact>` if you have information about
+any of these problems, even just to explain to me why you want them to start
+working properly.
 
 If your problem isn't discussed here, you can of course search the `coverage.py
 bug tracker`_ directly to see if there is some mention of it.
@@ -40,6 +40,10 @@ coverage.py from working properly:
   of these manipulate the C stack, and therefore confuse coverage.py.
   `Issue 149`_ has some pointers to more information.
 
+* `thread`_, in the Python standard library, is the low-level threading
+  interface.  Threads created with this module will not be traced.  Use the
+  higher-level `threading`_ module instead.
+
 * `sys.settrace`_ is the Python feature that coverage.py uses to see what's
   happening in your program.  If another part of your program is using
   sys.settrace, then it will conflict with coverage.py, and it won't be
@@ -50,7 +54,9 @@ coverage.py from working properly:
 .. _gevent: http://www.gevent.org/
 .. _greenlet: http://greenlet.readthedocs.org/
 .. _eventlet: http://eventlet.net/
-.. _sys.settrace: docs.python.org/library/sys.html#sys.settrace
+.. _sys.settrace: http://docs.python.org/library/sys.html#sys.settrace
+.. _thread: http://docs.python.org/library/thread.html
+.. _threading: http://docs.python.org/library/threading.html
 .. _issue 43: https://bitbucket.org/ned/coveragepy/issue/43/coverage-measurement-fails-on-code
 .. _issue 117: https://bitbucket.org/ned/coveragepy/issue/117/enable-coverage-measurement-of-code-run-by
 .. _issue 149: https://bitbucket.org/ned/coveragepy/issue/149/coverage-gevent-looks-broken
@@ -75,7 +81,8 @@ Really obscure things
 ---------------------
 
 * Python 2.5 had a bug (`1569356`_) that could make your program behave
-  differently when being measured with coverage.  This is diagnosed in `issue 51`_.
+  differently when being measured with coverage.  This is diagnosed in
+  `issue 51`_.
 
 .. _issue 51: http://bitbucket.org/ned/coveragepy/issue/51/turbogears-15-test-failing-with-coverage
 .. _1569356: http://bugs.python.org/issue1569356
@@ -84,5 +91,6 @@ Really obscure things
 Still having trouble?
 ---------------------
 
-If your problem isn't mentioned here, and isn't already reported in the `coverage.py bug tracker`_,
-please :ref:`get in touch with me <contact>`, we'll figure out a solution.
+If your problem isn't mentioned here, and isn't already reported in the
+`coverage.py bug tracker`_, please :ref:`get in touch with me <contact>`,
+we'll figure out a solution.