[TIP] examples of using epydoc programatically

[Titus Brown]

On Wed, May 09, 2007 at 01:23:28PM -0400, bear wrote:
-> basically I want the devs to treat the docstrings the same way they do the
-> code - any errors introduced into the docstrings are now only caught when I
-> start preparing for a release.
-> 
-> So I want to run epydoc, scan the output for errors and show that as a
-> tinderbox failure :)

Ahh!  I see.

Err, well, I don't know much about epydoc 3.0, but someone on the list
might...

--titus

-> On 5/9/07, Titus Brown <titus at caltech.edu> wrote:
-> >
-> >On Wed, May 09, 2007 at 02:00:20AM -0400, bear wrote:
-> >-> I'm working on some unit tests that will call epydoc to document
-> >modules and
-> >-> then run some reports on the logs.  While I had a handle on the much
-> >older
-> >-> version of epydoc we were using I'm having a hell of a time finding the
-> >code
-> >-> path to take with epydoc 3.
-> >->
-> >-> So instead of spending probably a good day mucking thru the source I
-> >figured
-> >-> I would drop a line here and see if anyone has some examples.
-> >
-> >Hey Bear!  What do you mean by "reports on the logs"?

-> -- 
-> ---
-> Bear
-> http://code-bear.com
-> 
-> Open Source Applications Foundation (OSAF)
-> http://www.osafoundation.org
-> 
-> PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822 40B3 CD29