Differences between revisions 29 and 31 (spanning 2 versions)
Revision 29 as of 2011-11-09 03:38:23
Size: 4704
Editor: JohnGabriele
Comment: Added link to the Gouda doc tool in "other documentation processing tools" section
Revision 31 as of 2013-08-28 17:36:52
Size: 4681
Comment: apydia is inactive
Deletions are marked like this. Additions are marked like this.
Line 27: Line 27:
 * Apydia, http://apydia.ematia.de/
Line 38: Line 37:
 * Apydia, http://apydia.ematia.de/
Line 52: Line 52:
 * [[http://www.unexpected-vortices.com/sw/gouda/docs/|Gouda]] -- a Python script (which uses Pandoc under the hood) to help make it as simple and easy as possible to write, organize, and publish docs.  * [[http://www.unexpected-vortices.com/sw/gouda/|Gouda]] -- a Python script (which uses Pandoc under the hood) to generate multi-chapter html documents from Markdown text files.

Python modules are usually documented using docstrings. You can read a module's docstrings from the Python interactive prompt with the help() function. For example:

import distutils

The help() function uses Python's standard pydoc module, as does the pydoc command that comes with Python.

The various documentation tools available generally do one of two things:

  • they either process docstrings in some way to make finding/reading documentation on a given module easier (so-called "API documentation tools"), or
  • they have nothing to do with docstrings and instead focus on processing documentation in some way (such as converting your plain text docs into html)

Currently, the Python docs consist of 2 parts:

  • the API docs that you can read using the help() command (pydoc can also provide these as html and even serve them from your local machine), and

  • the manuals/guides/howtos at http://python.org/doc/ which are written in reStructuredText (a plain text format) and processed into various output formats by the Sphinx tool.

When writing documentation for your own modules (either as manuals or docstrings (preferably both)), I suggest you use a plain text markup such as reST or Markdown.

Automatic Python API documentation generation tools

  • autosummary, an extension for the Sphinx documentation tool: http://sphinx.pocoo.org/ext/autosummary.html

  • autodoc, a Sphinx-based processor that processes/allows reST doc strings,

  • PyDoc, http://pydoc.org/ documentation browser (in HTML) and/or an off-line reference manual. Also in the standard library as pydoc

  • pydoctor, http://codespeak.net/~mwh/pydoctor/ replacement for now inactive Epydoc, pydoctor was born for the needs of Twisted project

  • Doxygen < http://www.doxygen.org > can create documentation in various formats (HTML, LaTeX, PDF, ...) and you can include formulas in your documentation (great for technical/mathematical software). Together with Graphviz < http://www.research.att.com/sw/tools/graphviz/ > it can create diagrams of your code (inhertance diagram, call graph, ...). Another benefit is that it handles not only Python, but also several other programming languages like C, C++, Java, etc.

No longer under development

Documentation processing tools

Other projects that can be used to produce API documentation

  • XIST - an XML based extensible HTML generator written in Python.

  • HtmlGen - a Python library for generating HTML documents.

Other documentation processing tools

  • Pandoc -- written in Haskell, this tool can read and write a number of formats (including reST).

  • Gouda -- a Python script (which uses Pandoc under the hood) to generate multi-chapter html documents from Markdown text files.


DocumentationTools (last edited 2019-07-03 12:34:58 by JaraKaca)

Unable to edit the page? See the FrontPage for instructions.