Python API documentation generation tool

Added a FAQ entry for this:

http://epydoc.sourceforge.net/faq.html#epytext_fail

Copying the docstring in question to a new file, and running epydoc on it,
gives us the following warning:

+------------------------------------------------------------------------------
| File /private/tmp/x/o.py, line 1, in o
| Warning: Line 40: Improper paragraph indentation.

Checking that line, we see it's:

@ivar def_out: Default output device to use for all
L{Task.Tools.Output.Output.say}
calls in this L{Perk} module.

The indent before "calls" is unexpected -- you need to either indent
L{Task.Tools.Output.Output.say} or dedent calls.

Epytext is a very "conservative" markup language. What I mean by that is
that if it sees anything that looks like it *might* not be epytext, it just
treats the docstring as plaintext instead. This makes it possible to run
epydoc on docstrings that were written without knowledge of epytext, which
eg contain ascii art, without getting gobledeygook as output.

If you find that a docstring is being rendered as plaintext, is almost
always means there's some epytext error in that docstring. Run epydoc on
that object, with -v, and check the warnings it generates.

-Edward