Doxygen will do Python as well as C, C++ and other languages: <a href="http://internetducttape.com/2007/03/20/automatic_documentation_python_doxygen/">http://internetducttape.com/2007/03/20/automatic_documentation_python_doxygen/</a> <a href="http://www.stack.nl/~dimitri/doxygen/docblocks.html#pythonblocks">http://www.stack.nl/~dimitri/doxygen/docblocks.html#pythonblocks</a> <div class="gmail_quote">On Sun, Jun 8, 2008 at 8:17 AM, David Farning <<a href="mailto:dfarning@gmail.com">dfarning@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">A very early alpha of the API documentation is now up at <a href="http://www.sugarlabs.org/%7Edfarning/" target="_blank">http://www.sugarlabs.org/~dfarning/</a> . The API are generated using epydoc which has a number of pros and cons. Pros:  Uses standard python docstrings- there is no commitment to epydoc in the future.  Very easy.  Docstrings can be extended using epytext, reStructuredText and Javadoc. Cons:  The parser is more strict than the standard python parser.  It catches some formatting errors that the python interrupter is able to handles. In many files the parser stopped before it reached the end of the file. I will put up a log file so developers can see what errors it is catching.  Epydoc only documents python files.  I haven't looked to deeply into the code but it looks like there are several c files in sugar-base and sugar-toolkit.  Do we want those documented? Thanks Dfarning _______________________________________________ Its.an.education.project mailing list <a href="mailto:Its.an.education.project@lists.lo-res.org">Its.an.education.project@lists.lo-res.org</a> <a href="http://lists.lo-res.org/mailman/listinfo/its.an.education.project" target="_blank">http://lists.lo-res.org/mailman/listinfo/its.an.education.project</a> </blockquote></div> -- "Always do right," said Mark Twain. "This will gratify some people and astonish the rest."