with examples and workaround. This keeps coming up, and I believe
that this section in the tutorial may have been (in part) the source
of the confusion. While it didn't show examples with [] for a default,
it also didn't emphasize enough why that would be a bad idea, and
while it did say that defaults are evaluated at the point of function
definition, the example was not relevant for this issue.
The text is almost completely from GvR's essay on packages; some
introductory paragraphs have been removed, and everything after the
'Details' section in the HTML has been dropped (seems too technical). A
paragraph has been added after the sample package layout stating that there
must be a file called__init__.py in a directory to make it a package.
file's existance).
Removed some XXX comments about extension modules which support pickling.
Added text from AMK about the readline and rlcompleter modules.
Thanks, AMK!
Moved stuff from "Recent Additions to 1.1" to "More on Defining Functions".
This means there's now a short section on "Defining Functions" immediately
followed by a long section "More on Defining Functions."
now requires LaTeX2HTML 98.1p1 or newer (& and is still in progress).
This means that doing things to change the formatting of the manuals (at the
"normal user" level, like A4 paper), can happen in just one place, rather
than in each document file.
Make all the indentations in {verbatim} environments have column 0 of the
listing in column 0 of the file.
Remove pagenumbering / pagestyle cruft.
Use more logical and less physical markup.
Use \file{} for file names.
Prefer \code{blat} and \emph{blat} to {\tt blat} and {\em blat}; this matches
current style in the Library Reference a bit better.
Made the example startup banner current. The version number should be
bumped before the next release.
since that's now the recommended way to do it.
In pickling discussion, change "code{pickle}" (not missing leading "\") to
"This" since the immediately preceeding sentence ended with the same text
(with the proper "\"). Fixes a formatting bug and an odd glitch in the
writing.
(and the contents it was supposed to be affecting). The latest
LaTeX2HTML handles these, but didn't close it as expected. This
handles that problem and does not affect the PostScript output.
Fred Drake