On 04/19/2010 04:06 PM, Lennart Regebro wrote: > On Mon, Apr 19, 2010 at 16:03, Lennart Regebro<rege...@gmail.com> wrote: >> On Mon, Apr 19, 2010 at 15:48, Marius Gedminas<mar...@gedmin.as> wrote: >>> If you've the discipline to keep the doctests short, I don't see why you >>> shouldn't continue writing them instead of unit tests >> >> Because they are a bitch to debug, relies on details of output, which >> makes them brittle, hard to port to Python 3, and can be tricky to set >> up with loads of subtle things like inheriting the environment from >> where the DocTest was created, etc. > > And from __future__ imports doesn't work. And.. I'm sure I'm gonna > remember more reason why doctests are bad later, but I can't be > bothered really.
Try defining a (persistent) class and sticking it into a ZODB. -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )