What about PythonDoc: http://effbot.org/zone/pythondoc.htm
PythonDoc is great because it parses source into an XML infoset that you can turn into whatever you want. It understands JavaDoc style tags, and you can make up your own tags as well.
Thanks Kevin. I think you suggested Pythondoc before and I forgot to follow up on it.
It certainly sounds like it could be customisable enough for us. I'm concerned that it uses comments rather than docstrings, although I see
there is support for docstrings as well.
It looks like it works by source code analysis rather than importing, which is another bonus. It is also fairly mature. Having our documentation represented as an XML documentation which we can format in any way would be good - if it picks up on all the detail we require.
I'll have a play with it and see how it goes for us.
Another one I know of, but never tried, is Endo:
https://svn.enthought.com/enthoug.../wiki/
EndoHowTo
part of the Enthought Tool Suite:
http://code.enthought.com/ets/
I like Pudge's layout more than the typical JavaDoc-style layouts, but it really is too bad it isn't really developed (except for the occasional bugfixes from those of us who use it).
I wrote up what I'd *like* to see in a documentation toolset here: http://blog.ianbicking.org/
decom...generation.html -- that way pieces of the toolset can continue to be developed without having to jump ship because of one missing feature.
There is also HappyDoc.
http://happydoc.sourceforge.net/
Depending on what you are doing you might be happier with LEO, though
it may be overkill. Leo is the sort of thing that you either love or hate.
http://sourceforge.net/projects/leo/
Commenting by HaloScan
