On Sat, Apr 17, 2010 at 19:17, Tres Seaver <tseaver@palladion.com> wrote:
I'm ambivalent about testing the Sphinx code snippets on each test run. I want those snippets to be *much* less comprehensive than they are currently, and am pretty sure that drift in the non-executable bits is at least as important a problem as drift in the snippets.
Well, unless they take of time, but they shouldn't, really. I think it's positive to get a quick feedback if you are breaking the documentation.
+0 on running them every time IFF we can find an easy way to run them during 'setup.py test' as well as buildout, and we continue to be mindful of the distinction between docs that work primarily as docs and tests that cover every code path.
I think manuel should solve that, we'll see, I'll have to test. I need to get manuel ported to Python 3 then too. :) -- Lennart Regebro: http://regebro.wordpress.com/ Python 3 Porting: http://python-incompatibility.googlecode.com/ +33 661 58 14 64