Javadoc style python manual?

John J. Lee jjl at
Fri Sep 8 22:41:56 CEST 2006

"Paul Boddie" <paul at> writes:
> Better usage of the find command could be made, and the resulting
> process occupied over 0.5GB before producing 581MB of API documents on
> disk. The resulting output reveals some major differences between some
> modules and in the quality of the documentation; for example, lots of
> empty docstrings cannot always be explained away by the --parse-only
> mode employed by epydoc in this case.

Why do you expect to get useful docs that way?  The canonical Python
stdlib docs live in LaTeX files, not in the docstrings.  You may find
some useful bits and pieces in the docstrings too, or you may not.


More information about the Python-list mailing list