pythonw.exe we just installed.  Making Windows key off the .pyw extension
instead screws people with multiple Python installations (reported more
than once on c.l.py).

was raised.  This occurred during installation.

generated filenames.

The logic for finding long matches before short ones was wrong (why did I never notice this??!?), fixed.

If there was a NULL registry key, Python could barf.

Also wraps some surrounding lines to 80 chars.

declarations, added some comments where I had to think too hard to
understand what was happening, and changed the primary internal get/set
functions to assert they're passed objects of the correct type instead of
doing runtime tests for that (it's an internal error that "should never
happen", so it's good enough to check it only in the debug build).

  interpreter the .spec file refers to.
Cosmetic tweaks.

It's hard to sort out what the bug was, exactly.  So, Big Hammer:

1. Python shouldn't be in the business of #define'ing NULL, period.
2. Users of the Python C API shouldn't be in the business of not including
   Python.h, period.

Hence:

1. Removed all #define's of NULL in Python source code (pyport.h and
   object.h).
2. Since we're *relying* on stdio.h defining NULL, put an #error in
   Python.h after its #include of stdio.h if NULL isn't defined then.

used to create the distribution and the creation date.

Takes care of the extra_path argument to the setup function,
installs the modules into <prefix>/extra_path and creates
a -pth file (like install_lib does).

for python installations, not only under HKEY_LOCAL_MACHINE.

Paid more attention to the comments on the report; Martin suggested just
not having a __del__() method, which makes more sense in this case.  So
I have removed it.

This closes SourceForge bug #113850.  Again.

The posixfile __del__ method attempts to close the file (_file_) it
contains. However, if the open() method fails, then _file_ is never
assigned.

This closes SourceForge bug #113850.

all, either to see whether the # of chars fit in an int, or that the
amount of memory needed fit in a size_t.  Checking these is expensive, but
the alternative is silently wrong answers (as in the bug report) or
core dumps (which were easy to provoke using Unicode strings).

Update processing of module synopsis tables (found at the beginning of
most chapters of the library reference) to reflect changes in the
processing pattern of recent versions LaTeX2HMTL.  Requires most
recent change to SynopsisTable.pm.

This does not fix the module index problem.

        exceptions which have interesting constructor signatures.

\pep, \seepep:  New macros.  Equivalent to \rfc and \seerfc, but
        referring to the PEP series instead of the Internet RFC
        series of documents.

table will be presented.  Accessor methods are used to access the
attribute.

input(), locals(), reload(), unicode(), and zip().

hyperlinks to relevant sections.

Clarify the conditions under which the "softspace" attribute of file-like
objects can "just work" (with relation to overriding of attribute access
in user-defined classes).

of the chapter.

Add explanation that this is only available when the cycle detector is
enabled at build time.

module sections.  Properly mark the name of the module in the content
of the reference there.

of the arrangement of other modules.

This closes SourceForge bug #110833.

PyOS_CheckStack now understands multiple threads. Other threads are not stack-checked, but at least they don't appear to always be out of stack.