includes some minor new inline markup and markup to generate hyperlinked
grammar productions.

Adopt a "style guide" document -- this beats writing our own and means
we'll have a chance at consistency, without having to make it all up
ourselves.

were generated by the use of the productionlist environment or the
\verbatiminput macro.

powerful latex2esis.py.

LaTeX and we have at least one occurance of that in the content, so this
script needs to support it as well.

re.findall doesn't take a maxsplit argument

translation more difficult, as well as reading the English more
difficult for non-native speakers.

clobbered on checkin.

found a bug here.  Here's the deal:

Class PyShell derives from class OutputWindow.  Method PyShell.close()
wants to invoke its parent method, but because PyShell long ago was
inherited from class PyShellEditorWindow, it invokes
PyShelEditorWindow.close(self).  Now, class PyShellEditorWindow itself
derives from class OutputWindow, and inherits the close() method from
there without overriding it.  Under the old rules,
PyShellEditorWindow.close would return an unbound method restricted to
the class that defined the implementation of close(), which was
OutputWindow.close.  Under the new rules, the unbound method is
restricted to the class whose method was requested, that is
PyShellEditorWindow, and this was correctly trapped as an error.

translation more difficult, as well as reading the English more
difficult for non-native speakers.

Add an index entry for the Telnet protocol.

Always refer to the protocol as Telnet instead of telnet.

additional offset is only applied to continuation lines for block
opening statements.

(py-compute-indentation): Only add py-continuation-offset if
py-statement-opens-block-p is true.

translation more difficult, as well as reading the English more
difficult for non-native speakers.

Symptom:  (1, 2, 3) <= (1, 2) returned 1.
This was already fixed in CVS for tuples, but an isomorphic error was in
the list richcompare code.

translation more difficult, as well as reading the English more
difficult for non-native speakers.

name when filling in the internal data structures, otherwise we incorrectly
raise a KeyError.

This fixes SF bug #432369.

the os.W*() functions used to interpret the return value.

This fixes SF bug #429361.

translation more difficult, as well as reading the English more
difficult for non-native speakers.

weren't functional under Windows even if enabled.

\platform statement.

Also fix a minor style consistency nit in an example.

empty.

values.  The change for attribute values matches the way Mozilla and
Navigator view the world, at least.

This closes SF bug #436621.

modules.

fewer arguments.

contains, tolist(), and the start/stop/step attributes.  This includes
removing the 4th ('repeat') argument to PyRange_New().

- make method reload handle __private attrs correctly
- fixed whole word search

Probable fix (the bug report doesn't have enough info to say for sure).
find_init_module():  Insist on a case-sensitive match for __init__ files.
Given __INIT__.PY instead, find_init_module() thought that was fine, but
the later attempt to do find_module("__INIT__.PY") didn't and its caller
silently suppressed the resulting ImportError.  Now find_init_module()
refuses to accept __INIT__.PY to begin with.
Bugfix candidate; specific to platforms with case-insensitive filesystems.

Return a reasonable name for the general macos exception (MacOS.Error).

solver.  In conjunction, they easily found a tour of a 200x200 board:
that's 200**2 == 40,000 levels of backtracking.  Explicitly resumable
generators allow that to be coded as easily as a recursive solver (easier,
actually, because different levels can use level-customized algorithms
without pain), but without blowing the stack.  Indeed, I've never written
an exhaustive Tour solver in any language before that can handle boards so
large ("exhaustive" == guaranteed to find a solution if one exists, as
opposed to probabilistic heuristic approaches; of course, the age of the
universe may be a blip in the time needed!).

We should not depend on two spaces between words, so use the white
space after the to-be-encoded word only as lookahead and don't
actually consume it in the regular expression.