directory that is not the source directory (ie, one created using
'/path/to/source/configure'.) Leaves this test very slightly degraded in
that particular case, compared to the build-in-sourcedir case, but that case
isn't a particularly strong test either: neither test the actual path that
will be used after installing. There isn't a particularly good way to test
this, and a poor test beats a failing test.

directory to the directory in which the setup.py script lived (which made
__file__ wrong)

fixed, with test that the script is run in the current directory of the caller

  controlled environment will more closely mirror the typical script
  environment.  This supports setup.py scripts that refer to data files.

Issue2290: Support x64 Windows builds that live in pcbuild/amd64.  Without it, sysutils._python_build() returns the wrong directory, which causes the test_get_config_h_filename method in Lib/distutils/tests/test_sysconfig.py to fail.

callable() from copy_reg.py, so the interpreter now starts up
without warnings when '-3' is given.  More work like this needs to
be done in the rest of the stdlib.

This change doesn't make any difference to CPython, but is a necessary fix for Jython.

Use vsbuild instead of devenv in build.bat and _bsddb.vcproj

Integrated bdist_wininst into PCBuild9 directory

The detection now works on Unix with Makefile, Makefile with VPATH and on Windows.

Fixed get_config_h_filename for Windows. Without the patch it can't find the pyconfig.h file inside a build tree.
Added several small unit tests for sysconfig.

The new msvc9compiler module supports VS 2005 and VS 2008. I've also fixed build_ext to support PCbuild8 and PCbuild9 and backported my fix for xxmodule.c from py3k. The old code msvccompiler is still in place in case somebody likes to build an extension with VS 2003 or earlier.
I've also updated the cygwin compiler module for VS 2005 and VS 2008. It works with VS 2005 but I'm unable to test it with VS 2008. We have to wait for a new version of cygwin.

and smtpd.py scripts that are installed by setup.py. That way, they
work when only "make altinstall" is used.

As discussed on distutils-sig: Allows the generated installer name on
64bit Windows platforms to be different than the name generated for
32bit Windows platforms.

As discussed on distutils-sig: Allows the generated installer name on
64bit Windows platforms to be different than the name generated for
32bit Windows platforms.

Move an import in mworkscompiler so that this module can be imported on
any platform.  Hopefully this works on all platforms.

even if package_dir is empty.

This needs to be backported.  I'm too tired tonight.  It would be great
if someone backports this if the buildbots are ok with it.  Otherwise,
I will try to get to it tomorrow.

(as opposed to the command line) will now write file names ending in
".cpp" too.

If MSVCCompiler.initialize() was called multiple times, the path
would get duplicated.  On Windows, this is a problem because the
path is limited to 4k.  There's no benefit in adding a path multiple
times, so prevent that from occuring.  We also normalize the path
before checking for duplicates so things like /a and /a/ won't both
be stored.

Will backport.

the 2.5.0 release.

directory within sys.exec_prefix.

lib/python/config, on "linux" and "gnu" systems.
Will backport.

file name mangling.
Will backport to 2.5.

installing .egg-info for a project that contains no modules or packages,
while using --root (as in bdist_rpm).

  bdist_rpm
Will backport to 2.5.