This is a temporary kludge and all is well in 3.3.

some functions like file.write().

If the version of zlib used to compile the zlib module is incompatible
with the one that is actually linked in, then calls into zlib will fail.
This can leave attributes of the z_stream uninitialized, so we must take
care to avoid segfaulting by trying to use an invalid pointer.

Fix by Richard M. Tew.

-j doesn't pass the memlimit on to child processes, so this doesn't work at
present, and even if it did, running multiple bigmem tests at once would
usually not be desirable (since you generally want to devote as much of the
available RAM as possible to each test).

The doc already points to argparse.

(this broken -F with e.g. test_multiprocessing)

same object as reader and writer, and deemphasize it in document order.

Even if Python is compiled on Linux 3.

normalization is different between unicode builds, so use a new non-BMP char and add normalization test

This fixes the use of Unicode identifiers outside the BMP in narrow builds.

Changes to crlf originally by Victor Stinner for 3.3, copied to lfcr by
me.  Manually tested.

The line about the test suite will still get printed for changes in
Tools for example, which aren’t covered by the test suite, but it’s not
a big deal IMO.

Fix closes Issue10087 -  fixing the output of calendar display in the html format. Patch by Chris Lambacher. Test Contributed by catherine.