On Thu, 2009-01-08 at 15:16 -0600, Ian Bicking wrote: > > Iain Duncan wrote: > >>> Writing a series of recipes (that can be tested automatically, probably > >>> with buildbot) might be a good addition? Figuring out how to write > >>> testable recipes is tricky, but a doable tricky. > >>> > >> This sounds like a very interesting project, I have been thinking of > >> something like that for some time. But as you said it quickly becomes > >> too large. If this gets narrowed down it could be a solid candidate. > >> Something like a code-review system meets wiki meets sphinx. It's so > >> useful that it could be used by other projects. In my initial search > >> for this someone point me out to http://docs.scipy.org/doc/ > > > > I think the way to do that is with doc test code in sphinx. The fact > > that you can hide code that still runs means you can make a recipe bit > > by bit and still be able to test the whole shebang by using the doctest > > builder. But I expect everyone already knows this... ;-) > > I've tried that, and it's really hard to manage. A full application > layout is hard to define in doctest. And just generally if you want to > present the evolution of an application, it's hard to maintain generally > (e.g., you detect an error in step 3 and you have to backport it to step > 2 and 1). Also doctesting HTML output kind of sucks, even if you try to > be really minimalistic in your output.
Good to know, thanks for the tip. That'll save me trying to take that idea too far for my own project. Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
