[Python-checkins] devguide: Clarify some things about how to find out what modules need some coverage help.

[brett.cannon]

brett.cannon pushed 0ed7176efa98 to devguide:

http://hg.python.org/devguide/rev/0ed7176efa98
changeset:   54:0ed7176efa98
tag:         tip
user:        Brett Cannon <brett at python.org>
date:        Sat Jan 08 14:23:58 2011 -0800
summary:
  Clarify some things about how to find out what modules need some coverage help.

files:
  coverage.rst

diff --git a/coverage.rst b/coverage.rst
--- a/coverage.rst
+++ b/coverage.rst
@@ -23,12 +23,17 @@
 overall view of how good coverage is for various modules (you will want to
 focus on those in the ``Lib`` directory as those are the pure Python modules
 from Python's stdlib, and thus easier to work with than the C extension
-modules). Another is to follow the examples below and simply see what kind of
+modules). But since this is a third-party site we cannot promise that it will
+always be accessible or have useful information (i.e., be working properly).
+
+Another is to follow the examples below and simply see what kind of
 coverage your favorite module has. This is "stabbing in the dark", though, and
-so it might take some time to find a module that needs coverage help. Finally,
-you can simply run the test suite yourself with coverage turned on and see what
-modules need help. This has the drawback as the test suite takes some time to
-complete when run under coverage measuring.
+so it might take some time to find a module that needs coverage help.
+
+Finally, you can simply run the entire test suite yourself with coverage turned
+on and see what modules need help. This has the drawback as the test suite
+takes some time to complete when run under coverage measuring, but you will
+have an accurate, up-to-date notion of what modules need the most work.
 
 
 Using coverage.py

--
Repository URL: http://hg.python.org/devguide