\lineiv:  Row for {tableiv}.

before I remove all this cruft.

of mkdir(), rmdir() and rename() that make or remove intermediate
directories as well.

of mkdir(), rmdir() and rename() that make or remove intermediate
directories as well.

SynopsisTable objects are used to store the table of module synopses for
a single chapter it the manual.

get a decent error message when it's not a string (instead of
confusing errors when trying to use the thing).

this is the shortest chapter.)

Hurray, I'm done with this!

previously undocumented features.

Packages and the import mechanism in general are still left
undocumented.

Fix some comments.

For lib.pdf, run tools/toc2bkm.py to get "bookmarks" in acroread.

acroread.  The problem this solves is likely dependent on font availability,
so keeping things simple is a good solution.

it's mentioned.

Fix style dependencies for HOWTO documents.

case.  Two modules (SocketServer, BaseHTTPServer) still don't match; those
names are just too long!

Python Library Reference.  The other manuals do not suffer.

This does not affect HOWTO documents.

Add item about howto docs that use \localmoduletable problem for howto
documents.

(complex numbers, power operator).

	courier font used in Python code.  This still isn't *good*, but
	makes the width about right in most cases.  (Exception: it's now
	a little wide in \var words.)

Clean up some of the markup.

reflect its new place in the exception hierarchy; fixed typos, etc.

equivalent to exceptions.OSError.

for this chapter.  This protects against backend changes for \declaremodule.

	in a HOWTO document isn't listed in the synopsis table twice.  This
	will do until the real bug is found (low priority!).

macros.

of three macros, one which replaces some of the current conventions used in
the module sections:

  \declaremodule:  Requires two parameters: module type (standard, builtin,
	extension), and the module name.  An optional parameter should be
	given as the basis for the module's "key" used for linking to or
	referencing the section.  The "key" should only be given if the
	module's name contains underscores, and should be the name with the
	underscore's stripped.  This should be the first thing after the
	\section used to introduce the module.

  \modulesynopsis:  Requires a single parameter: a short, one-liner
	description of the module that can be used as part of the chapter
	introduction.  This should probably be placed just after the
	\declaremodule, but may be placed anywhere in the same section.

  \localmoduletable:  No parameters.  If a .syn file exists for the current
	chapter (or for the entire document in howto docs), a synopsistable
	is created with the contents loaded from the .syn file.

Some re-organization due to module synopsis support.

Some \def's changed to \newcommand's.