This was a regression caused by the hash randomization patch.

BSD's make doesn't support some of the features.

sporadic crashes in multi-thread programs when several long deallocator
chains ran concurrently and involved subclasses of built-in container
types.

Because of this change, a couple extension modules compiled for 3.2.4
(those which use the trashcan mechanism, despite it being undocumented)
will not be loadable by 3.2.3 and earlier. However, extension modules
compiled for 3.2.3 and earlier will be loadable by 3.2.4.

and StringIO objects now raise ValueError when the object has been closed.
Patch by Alessandro Moura.

Patch by Anton Barkovsky, comment addition by me.

This showed up as a bug in 3.3 because the definition for Chrome
produced such an empty string.  This fix is tested in 3.3+;
backporting the new test suite is more trouble than it is worth.

Before, the type function was called twice in the case where the default
was specified and the argument was given as well.  This was especially
problematic for the FileType type, as a default file would always be
opened, even if a file argument was specified on the command line.

Patch by Arnaud Fontaine, with additional test by Mike Meyer.

Patch by Mike Hoy.

Fix issue 13370: Ensure that ctypes works on Mac OS X when Python is compiled using the clang compiler

Patch by Chris Rebert.

Closes #9374: add back now-unused module attributes; removing them is a backward compatibility issue, since they have a public-seeming name.

Fix by Colin Su.  Test by me, based on a test written by Petri Lehtinen.

It was exposed by 03c98d05b140 and dbbf3ccf72e8.

(Patch by Ronald Oussoren)

This is due to an off-by-one error: the allocated buffer didn't have room for a NUL
character at the end of the mbstowcs result.

This is necessary for ZFS systems, which don't support UF_IMMUTABLE.