This closes SourceForge patch #101714.

is where all the FAQs about extension-building will be answered.

'util.byte_compile()'.  Currently just reproduces the existing functionality
-- doesn't use any of the fancy features in the new 'byte_compile()'.

standard 'py_compile.compile()' function.  Laundry list of features:
  - handles standard Distutils 'force', 'verbose', 'dry_run' flags
  - handles various levels of optimization: can compile directly in
    this interpreter process, or write a temporary script that is
    then executed by a new interpreter with the appropriate flags
  - can rewrite the source filename by stripping an optional prefix
    and preprending an optional base dir.

Fixed 'subst_vars()' so it actually blows up like the docstring claims
  (and fixed the docstring not to claim it handles ${var}, which it
  doesn't).

absolute pathnames; this lets it keep working in the face of chdir'ing
around.

unicodedata_db.h.

on the module file -- could be useful for subclasses overriding it.

this will please everyone (as if that's possible).

'uname()' -- specifically NeXTSTEP.

  - added 'sub_commands' class attr
  - added 'has_*()' predicates referenced by the sub-command list
  - rewrote 'run()' so it's a trivial loop over relevant sub-commands

appear as methods on socket objects.

Error reported via email by Pete Shinners <pete@visionart.com>.

Fixed some indentation inconsistencies.

                               elsewhere in 1.5.2.

Add PyModule_AddStringConstant and PyModule_AddObject if version <2.0,
to allow to share this file with PyXML.

<grant.griffin@honeywell.com>.

complex objects, and explain how to build so that Objects/complexobject.c
is compiled without optimization.

Closing SourceForge bug #110695 as "Won't Fix".

This closes SourceForge bug #115673.

<grant.griffin@honeywell.com>.

Fixed displays of the interactive prompt in running text.
These close SourceForge bug #115658.

Also:

Updated discussion of tuple unpacking to reflect the general ability
to unpack any sequence type.  Explained that it is possible to create
tuples which contain mutable values, and noted in the dictionary
section that such tuples cannot be used as keys.

Noted that .pyc and .pyo files can be run directly when provided as
the script parameter to the interpreter, and slightly clarified
comments about using modules with only the byte compiled code.

Removed some XXX comments that are no longer relevant.
Removed commented-out paragraph about __private names being experimental.

Adjusted markup for consistency in some places.

They are unneeded: All this stuff is already done by the
install command which is run by bdist_wininst.

One bug has been fixed:
The root of the fake install tree is install.install_purelib,
not install.install_lib!
They are different if the extra_path option is used in
the setup function.

Rebuild after the changes to wininst.exe.

unintentionally caused them to get written in text mode under Windows.
As a result, when .pyc files were later read-- in binary mode --the
magic number was always wrong (note that .pyc magic numbers deliberately
include \r and \n characters, so this was "good" breakage, 100% across
all .pyc files, not random corruption in a subset).  Fixed that.

most modern Unix flavors.

The age of this portion of the README was noted in SourceForge bug #115625.

from sources, not in general.

This closes SourceForge bug #115608.

    friends.  (Modified version of patch #101682 from Neil Schemenauer)

for Windows & Unix.