Differences between revisions 25 and 26
Revision 25 as of 2010-10-08 11:01:46
Size: 4465
Editor: MichaelFoord
Comment:
Revision 26 as of 2010-10-08 11:05:41
Size: 4500
Editor: MichaelFoord
Comment:
Deletions are marked like this. Additions are marked like this.
Line 23: Line 23:
 * [[http://sphinx.pocoo.org/ext/autodoc.html|autodoc]], a Sphinx-based processor that processes/allows reST doc strings,
Line 24: Line 25:
 * EpyDoc, http://epydoc.sourceforge.net/
Line 30: Line 30:
 * [[https://svn.enthought.com/enthought/wiki/EndoHowTo|Endo]] from Enthought Tool Suite - generates HTML API documentation from docstrings and from plain comments that immediately precede variable assignments.
 * [[http://sphinx.pocoo.org/ext/autodoc.html|autodoc]], a Sphinx-based processor that processes/allows reST doc strings,
Line 34: Line 32:
= No longer under development =

 * EpyDoc, http://epydoc.sourceforge.net/
 * [[https://svn.enthought.com/enthought/wiki/EndoHowTo|Endo]] from Enthought Tool Suite - generates HTML API documentation from docstrings and from plain comments that immediately precede variable assignments.
 * [[http://pudge.lesscode.org/|Pudge]] (defunct)
Line 35: Line 38:
 * [[http://pudge.lesscode.org/|Pudge]] (defunct)

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
help(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

No longer under development

  • EpyDoc, http://epydoc.sourceforge.net/

  • Endo from Enthought Tool Suite - generates HTML API documentation from docstrings and from plain comments that immediately precede variable assignments.

  • Pudge (defunct)

  • HappyDoc (not supported) - documentation extraction tool that uses the parse tree for a module to derive the information used in its output, rather that importing the module directly.

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).


CategoryDocumentation

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

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