SF patch #471839: Bug when extensions import extensions (Shane Hathaway)

    When an extension imports another extension in its
    initXXX() function, the variable _Py_PackageContext is
    prematurely reset to NULL. If the outer extension then
    calls Py_InitModule(), the extension is installed in
    sys.modules without its package name. The
    manifestation of this bug is a "SystemError:
    _PyImport_FixupExtension: module <package>.<extension>
    not loaded".

    To fix this, importdl.c just needs to retain the old
    value of _Py_PackageContext and restore it after the
    initXXX() method is called. The attached patch does this.

    This patch applies to Python 2.1.1 and the current CVS.

"cvs admin -kb installer.bmp" (although this should be unneeded?).

but apparently didn't get backstitched into NEWS before the release.
Trimmed trailing whitespace.

+ Lib/site-packages wasn't created on Windows in 2.1.
+ The compiler package lived in Tools instead of in Lib.

After this, a directory compare of an installed 2.1.1 and an installation
created by this installer "are close".  The remaining differences have to
do with files that the old installer mistakenly never knew existed (like
the distutils README, and pynche's color-name files).  All such cases in
2.1.1 were bugs, now repaired in 2.1.2.

2.1 (e.g., there was no Lib/test/data directory then, hotshot didn't exist,
ditto the Lib/email package, etc).  Also restored the now-obsolete expat
setup.

2002!).  Does anyone know of a copyright blurb I missed?

closer.

more cleanly (I think this supports more Linux systems; not sure).
Barry Warsaw & Martin von Loewis actually agree on this!
This closes SF patch #502023.

copied here verbatim from the trunk (it should be release-independent).

  Fix the second reincarnation of SF #456395 -- failure on IRIX.  This
  time use .replace() to change all \r\n into \n, not just the last one.

This makes test_pty work on Irix.

Closes patch:
[ #481080 ] Read Me file Patch for Python 2.1.2

sent with empty message.

sheesh. Lucky I decided it was worth doing last minute complete compile
tests. cvs merge stupid on my part fixed that made solaris builds totally
fail.

Added documentation of the sendall() method, and a note to the send() method
that it does not guarantee that all data is sent.

Thread.__bootstrap(): ignore exceptions in the self.__delete() call in
the finally clause.  An exception here could happen when a daemon
thread exits after the threading module has already been trashed by
the import finalization, and there's not much of a point in trying to
insist doing the cleanup in that stage.

This should fix SF bug ##497111: active_limbo_lock error at program
exit.

os.system().
This closes Python bug #500401, Debian bug #127507.

manually with, e.g.:
    CC='gcc -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64' ./configure

Based on comment sent to python-docs.