Reviewed by Amaury Forgeot d'Arc.

universal builds that are presented by the configure script.

Reviewed by Benjamin Peterson.

later test failures.  As discussed on #python-dev

non-ascii characters and Unicode in setup.py meta-data.

from the same python instance, some environment variables (LIB, INCLUDE)
would grow without limit.

Tested with these statements:
    distutils.ccompiler.new_compiler().initialize()
    print os.environ['LIB']
But I don't know how to turn them into reliable unit tests.

Be less strict when parsing these version numbers,
they don't necessarily follow the python numbering scheme.

This patch adds a new configure argument on OSX:
        --with-universal-archs=[32-bit|64-bit|all]

When used with the --enable-universalsdk option this controls which
CPU architectures are includes in the framework. The default is 32-bit,
meaning i386 and ppc. The most useful alternative is 'all', which includes
all 4 CPU architectures supported by MacOS X (i386, ppc, x86_64 and ppc64).

This includes limited support for the Carbon bindings in 64-bit mode as well,
limited because (a) I haven't done extensive testing and (b) a large portion
of the Carbon API's aren't available in 64-bit mode anyway.

I've also duplicated a feature of Apple's build of python: setting the
environment variable 'ARCHFLAGS' controls the '-arch' flags used for building
extensions using distutils.

Python

the testsuite.

If configparser is unavailable, try to import configparser using its
old name. This is required for backward-compatibility with older
Python versions.

The distutils module should continue to use the old ConfigParser name,
for backward-compatibility.