diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2009-06-13 16:44:22 -0400 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2009-06-13 16:44:22 -0400 |
| commit | 69b4f062834f8f249c6005b89c13b8284fbda378 (patch) | |
| tree | 860687cd3ba6c926d2bba5c00770460c29629b3f | |
| parent | 69b7c212b27b4fc046f693f080b6cbcbcbda89d3 (diff) | |
| download | python-coveragepy-git-69b4f062834f8f249c6005b89c13b8284fbda378.tar.gz | |
Give every page a history timestamp of now.
| -rw-r--r-- | doc/api.rst | 1 | ||||
| -rw-r--r-- | doc/changes.rst | 1 | ||||
| -rw-r--r-- | doc/cmd.rst | 1 | ||||
| -rw-r--r-- | doc/index.rst | 1 |
4 files changed, 4 insertions, 0 deletions
diff --git a/doc/api.rst b/doc/api.rst index 951ddb42..17f74b64 100644 --- a/doc/api.rst +++ b/doc/api.rst @@ -5,6 +5,7 @@ Coverage API ============ :history: 20090524T134300, brand new docs. +:history: 20090613T164000, final touches for 3.0 The API to coverage.py is very simple, contained in a single module called coverage containing a single class, also called coverage. Methods on the diff --git a/doc/changes.rst b/doc/changes.rst index d7c0d735..b420e6f7 100644 --- a/doc/changes.rst +++ b/doc/changes.rst @@ -1,6 +1,7 @@ .. _change:
:history: 20090524T134300, brand new docs.
+:history: 20090613T164000, final touches for 3.0
------------------------------------
Major change history for coverage.py
diff --git a/doc/cmd.rst b/doc/cmd.rst index 0a9f0f68..9f945193 100644 --- a/doc/cmd.rst +++ b/doc/cmd.rst @@ -5,6 +5,7 @@ Coverage command line usage =========================== :history: 20090524T134300, brand new docs. +:history: 20090613T164000, final touches for 3.0 .. highlight:: console diff --git a/doc/index.rst b/doc/index.rst index 221c06a1..f7eed9d8 100644 --- a/doc/index.rst +++ b/doc/index.rst @@ -3,6 +3,7 @@ coverage.py ===========
:history: 20090524T134300, brand new docs.
+:history: 20090613T164000, final touches for 3.0
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
|