Ideally do this with a clean checkout on your Windows machine too. Assuming you have setup your compilers etc appropriately just do this:

C:\python26\python setup.py build
C:\python26\python setup.py test

C:\python27\python setup.py build
C:\python27\python setup.py test

C:\python33\python setup.py build
C:\python33\python setup.py test

If you are using MinGW, do not forget to add --compiler=mingw32 (or make it the default on distutils, see the step on building on windows machines). Also If you are using a modern MinGW compiler, then distutils of Python will use an option (-mno-cywgin) that is deprecated and will break gcc. A possible solution is to edit distutils

Running the tests simultaneously is risky, as two threads may both try and read/write to the same temp files.

17. On your windows machine, build the Windows installers (either from a clean checkout, or the an unzipped copy of the source code bundle made earlier). Build the installers first, if you do a build/test/install before hand you seem to get a bloated setup exe. Assuming you have setup your compilers etc appropriately just do this:

If you are using MinGW, you will have to make distutils use it (it will use a MS compiler by default). Here (contrary to the build step) you cannot pass the compiler as a parameter. The best solution might be to configure distutils