Once I see how the buildbots react, I'll backport this to 2.4.

platforms that don't support changing thread stack size.

sys.stdin is closed.

the md5 and sha modules, so add it in Modules/Setup.dist too.

Passing float arguments to struct.pack when integers are expected
now triggers a DeprecationWarning.

Fix the name of the pdb file as well.

The '-mimpure-text' linker flag is required when linking _ctypes.so.

In the 2.5 development cycle, MAKE_CLOSURE as changed to take free
variables as a tuple rather than as individual items on the stack.
Closes patch #1534084.

in the byte code and co_consts even if they were not used, ie
immediately popped off the stack.

on each iteration.  I'm not positive this is the best way to handle
this.  I'm also not sure that there aren't other cases where
the lnotab is generated incorrectly.  It would be great if people
that use pdb or tracing could test heavily.

Also:
 * Remove dead/duplicated code that wasn't used/necessary
   because we already handled the docstring prior to entering the loop.
 * add some debugging code into the compiler (#if 0'd out).

str(exception) raised an exception.

for stream decoder, but final=True for the decode function.

Document that using the wrong calling convention can also raise
'ValueError: Procedure called with the wrong number of arguments'.

a socket operation on a socket with a timeout, the exception will be
caught correctly.  Previously, the exception was not caught.

writing the crc to file on the "PPC64 Debian trunk" buildbot
when running test_tarfile.

This is again a case where the native zlib crc is an unsigned
32-bit int, but the Python wrapper implicitly casts it to
signed C long, so that "the sign bit looks different" on
different platforms.

Reported by Klocwork #36

buildbot (& possibly other 64-bit boxes) during test_gzip.

The native zlib crc32 function returns an unsigned 32-bit integer,
which the Python wrapper implicitly casts to C long.  Therefore the
same crc can "look negative" on a 32-bit box but "look positive" on
a 64-bit box.  This patch papers over that platform difference when
writing the crc to file.

It may be better to change the Python wrapper, either to make
the result "look positive" on all platforms (which means it may
have to return a Python long at times on a 32-bit box), or to
keep the sign the same across boxes.  But that would be a visible
change in what users see, while the current hack changes no
visible behavior (well, apart from stopping the struct deprecation
warning).

Note that the module-level write32() function is no longer used.