I made a note a month ago that install --record wrote incorrect entries
for extension modules (I think the problem was that the first character
of the file was stripped), so I’m now adding a test to try to reproduce
that in the current versions.

I need this to fix the failing test_install.

I need to copy this file in another test too, so I moved the support
code to distutils.tests.support and improved it:

- don’t skip when run from the Lib/distutils/tests directory
- use proper skip machinery instead of custom print/return/test suite
  fiddling.

Text adapted from the PEP.  Addition requested by Terry J. Reedy on
2011-02-23 on python-dev.

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