[py-dev] capturing / doctests / py lib release

[Michele Simionato]

On 4/30/05, holger krekel <hpk at trillke.net> wrote:
> I consider the "how to collect doctests"
> issues still the primary blocker design question.

I have some utility to do that (in the category "it works for me").
Given a package, it walks recursively on all submodules and subpackages,
retrieving docstrings and executing them. At the end it returns a simple
summary. Originally, I wanted to convert those doctests to unittests
(it is actually trivial) but I did not need that, so I thought "why bother?". 
Also, very often I have doctests in external files, and I would like 
to collect them too. Life would be simpler however if there was a
set of common conventions (i.e. doctest files have a specific
extension, they go in a specific directory) etc.
Does somebody know how they do that in Zope3 ? 
They for sure have *lots* of doctests.

              Michele Simionato