From b693824211b564fd1746950a4ddd0602eb942bf1 Mon Sep 17 00:00:00 2001 From: Ned Batchelder Date: Sat, 13 Jun 2009 21:31:10 -0400 Subject: Record stuff I'm not doing now so I can do it later. --- TODO.txt | 11 +++++++---- doc/faq.rst | 2 +- 2 files changed, 8 insertions(+), 5 deletions(-) diff --git a/TODO.txt b/TODO.txt index 040933c8..cb33ac65 100644 --- a/TODO.txt +++ b/TODO.txt @@ -100,8 +100,8 @@ x Tricky swapping of collector like figleaf, pycov, et al. (Don't need to do * Community -- New docs, rather than pointing to Gareth's - - Min python version is 2.3. ++ New docs, rather than pointing to Gareth's + + Min python version is 2.3. - Three phases of work: - Collection - Analysis @@ -114,11 +114,14 @@ x Tricky swapping of collector like figleaf, pycov, et al. (Don't need to do - Bare "except:" lines now count as executable code. - Double function decorators: all decorator lines count as executable code. - Document the .coverage file format. - - HTML reporting. + + HTML reporting. + Be sure --help text is complete (-i is missing). + Host the project somewhere with a real bug tracker: bitbucket.org -- Point discussion to TIP ++ Point discussion to TIP - PEP 8 compliance? +- References between pages are off: + - They have tags around them. + - They use #anchors that don't survive the px->html conversion. * Programmability diff --git a/doc/faq.rst b/doc/faq.rst index 54be5656..2a2d6054 100644 --- a/doc/faq.rst +++ b/doc/faq.rst @@ -32,7 +32,7 @@ to run your program with coverage, then your entire program will be monitored. If you are using the :ref:`API `, you need to call coverage.start() before importing the modules that define your functions. -**Q: Does coverage work on Python 3.0?** +**Q: Does coverage work on Python 3.x?** Not yet, but that's next on my list. -- cgit v1.2.1