Lennart Regebro wrote: > On Wed, Dec 30, 2009 at 11:51, Chris Withers <[email protected]> wrote: >> Lennart Regebro wrote: >>> So. I want either to get a normal unittest.TextTestRunner().run(suite) >>> to include the testcode blocks, *or* I need to override the testparser >>> for sphinx. Any recommendations for how to do this? Looking into how >>> sphinx.ext.doctest works, I believe the first option is >>> hellacomplicated. Is there a way for the second one? >> I think you should look at Manuel: >> >> http://packages.python.org/manuel/ > > Well, I was able to make it run with my own parser.
What "it" are you referring to? > However, it still completely refuses to execute any codeblock stuff > (or at least reports no error, even though the code is invalid). It's > also not clear to me how the output of a codeblock would be tested. Manuel's codeblock execution is exactly that, output is ignored and lost. However, exceptions will propagate through, so they and particularly hidden code blocks make for great testing.. See: http://packages.python.org/checker/use.html and http://packages.python.org/checker/_sources/use.txt (it includes some "from __future__" stuff for good measure :-) ) cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
