Windows/Python builds of 1.5

[Adrian Wilkins]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I was wondering where these had got to ; mostly because I have a small
number of patches for the stock bzrlib which are either non-production
quality or possibly unwanted, but I find useful, so the "exe" version
isn't as flexible to me (I just branch my local bzr.dev, hack on it, and
merge the changes to my installed folder as applicable).

Since an "exe" installer but not "Python" installers had materialised, I
had a shufty at the wiki pages for this and built my own installers. It
turned out to be much easier than I thought, largely because I'd already
done the donkey work setting up compilers and Pyrex when I was trying to
build Jelmers Pyrex bindings for SVN.

So I have a build of the Python-flavoured installers languishing on my
disk, and I was wondering if you lot trust me enough to want me to
upload it. I'd probably also recommend that it gets verified by someone
else because I really did just install Python 2.4 and Pyrex (again),
write the version-calling batch files, and run the make script.

For the record, the Pyrex extensions were built using the MSVC 2003
compiler from the Visual C++ 2003 toolkit (which you have to hunt around
to find).

I remember there being a long-standing misconception in the SVN team
that because Python 2.4 was built with the VS 2003 compiler, that they
couldn't build bindings for 2.4 (whereas they actually could, as long as
they were statically bound). What's the situation with compilers as far
as Python goes now - are there reasons not to use newer compilers, what
are they, etc? Do we prefer the the MinGW compiler suite (for either
technical or political reasons) or are the (arguably better optimized)
MS compilers good enough? The C++ compiler installed in the Windows SDK
is now the full optimizing compiler (as it appeared in VS2005, minus an
/analyze switch).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD4DBQFIPAuLcP1uebIhWSYRAq5oAJizYJFWvW7cf2q/YFLPUemrtZcrAJwKqiga
2ATqzknvwG50FavruRzmXA==
=DtDo
-----END PGP SIGNATURE-----