Prompted by a discussion on comp.lang.python.

skip over functions with private names (as indicated by the underscore
naming convention).  The old default created too much of a risk that
user tests were being skipped inadvertently.  Note, this change could
break code in the unlikely case that someone had intentionally put
failing tests in the docstrings of private functions.  The breakage
is easily fixable by specifying the old behavior when calling testmod()
or Tester().  The more likely case is that the silent failure was
unintended and that the user needed to be informed so the test could be
fixed.

these make sense even without that processing chain.

conversion to support.  Keep the content as normal content, with a
note that this applies starting in Python 2.3.

The !PyType_Check(base) check snuck in as part of rev 2.215, but was
unrelated to the SF patch that is mentioned in the checkin comment.
The test is currently unnecessary because base is set to the return
value of best_bases(), which returns a type or NULL.

by controling the font.

- added missing period
- added markup so it's easier to tell which names are special

- more clean up of the generated import library definiton (.DEF file)
  following checking of patch 770521, and tightening of the sed regexps.

- use -O3 even with gcc 2.8.1 - worth nearly 10% with 2.3; worth
  nothing with 2.2.x.

- clean up a couple of whitespace issues introduced by a cut'n'paste.

were in the wrong file.  Moved out of libstring.tex and into
libstdtypes.tex.

unittest environment.  Since his extension finds docstrings in private
functions, it exposed a bug in the difflib doctests.

Note, these tests were not getting exercised because
doctest skips over private functions.

- add support for the "What's New" document
- add short aliases for individual documents; nice for debugging
  conversions

GNU info conversion.

better accomodate the GNU info conversion.

encoding.  Use sys.getfilesystemencoding().

be included in the \var.  This produced weird results in general, but
broke the GNU info conversion.

characters); \AA is used in whatsnew23.tex.

Extensions must still be configured manually and there is currently one
set of extension key bindings for all platforms.

Bring NEWS.txt up to date.

Update CREDITS.txt and idlever.py for release.

M NEWS.txt
M config-extensions.def
M extend.txt
M help.txt
M idlever.py

sys.__modules__.

If the initial import of warnings fails, clear the error.  When the module
is actually needed, if the original import failed, see if it has managed
to find its way to sys.modules yet and if so, remember it.

text.  There needs to be a better way.

  - fix comment describing what this is for
  - add lots of indexing macros to this call
Closes SF bug #518989.

Pertains to SF bug #518989.

Checking // would call floor division but did not test that
true division had become the default with 'from __future__ import division'.

Checking // would call floor division but did not test that
true division had become the default with 'from __future__ import division'.

Closes SF bug #453683.

Bug fix candidate.

Fixes for three related bugs, including errors that caused a script to
be ignored without printing an error message.  The key problem was a bad
interaction between syntax warnings and syntax errors.  If an
exception was already set when a warning was issued, the warning could
clobber the exception.

The PyErr_Occurred() check in issue_warning() isn't entirely
satisfying (the caller should know whether there was already an
error), but a better solution isn't immediately obvious.

Bug fix candidate.

[Patch #708374] Only apply the check for file size if the file is a regular file, not a character or block device.