<br><br><div><span class="gmail_quote">On 5/10/07, <b class="gmail_sendername">Daniele Varrazzo</b> <<a href="mailto:piro@develer.com">piro@develer.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Hello bear, and list,</blockquote><div><br>Hi Daniele - thanks for responding.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
What do you want to test about the documentation? Do you want to write a test<br>that programmatically calls epydoc and fails if any of what Epydoc considers an<br>error is signaled in the log (such as bad reST format, missing link target...)?
<br>In this case Epydoc has an handy facility: you can define your own `log.Logger`<br>subclass storing any relevant record into its state and register it using<br>`log.register_logger()`. After an epydoc run your logger state may tell you if
<br>any error has been found.</blockquote><div><br>Almost exactly what I want to do - I'm not worried about the log.Logger setup as my test framework is already capturing all the stdout/stderr output. <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The `main()` in the `cli` module [1] gathers the options from the command line<br>and config file and run the documentation build (line 738). The same module<br>contains examples of `log.Logger` subclasses, such as the one used to generate
<br>an HTML log page in documentation is built in HTML format (line 1348), and<br>their registration (line 687).</blockquote><div><br>I was trying to find some examples that didn't require pushing arguments onto args[] and then calling the
cli.main() routine as I'm already inside of a program that has already parsed the command line for it's own options.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You may also look for help in the Epydoc mailing list.<br>[1] <a href="http://epydoc.svn.sourceforge.net/viewvc/epydoc/trunk/epydoc/src/epydoc/cli.py?revision=1585&view=markup">http://epydoc.svn.sourceforge.net/viewvc/epydoc/trunk/epydoc/src/epydoc/cli.py?revision=1585&view=markup
</a></blockquote><div><br>ick, sourceforge mailing lists give me a rash - but I didn't realize the list was active so I will transfer my question over to it - thanks!<br> </div></div>---<br>bear<br><br>Build and Release Engineer
<br>Open Source Applications Foundation (OSAF)<br><a href="mailto:bear@osafoundation.org">bear@osafoundation.org</a><br><a href="http://www.osafoundation.org">http://www.osafoundation.org</a><br><br><a href="mailto:bear@code-bear.com">
bear@code-bear.com</a><br><a href="http://code-bear.com">http://code-bear.com</a><br><br>