I think it is reasonable that if you want to *build* a package, then you need to have the build tools, such as a compiler and standalone python. I think pre-built packages for dulwich and bzr-git could be made without requiring them to be part of the standard windows installer. That said, somebody would have to do it, and so far nobody has done so. John =:-> <div class="gmail_quote">On Sep 5, 2011 7:41 AM, "Eli Zaretskii" <<a href="mailto:eliz@gnu.org">eliz@gnu.org</a>> wrote: >> From: "Stephen J. Turnbull" <<a href="mailto:stephen@xemacs.org">stephen@xemacs.org</a>> >> Cc: Martin Pool <<a href="mailto:mbp@canonical.com">mbp@canonical.com</a>>, >> <a href="mailto:bazaar@lists.canonical.com">bazaar@lists.canonical.com</a> >> Date: Mon, 05 Sep 2011 13:05:05 +0900 >> >> I don't recall any traffic on python-devel regarding building Python >> with non-MS toolchains, except for the occasional statement that it's >> possible (maybe even supported in some sense). The PSF and Active >> State Python installers are built with MS tools, and I would guess >> that the great majority of Windows installs are one of those two. It >> would be asking for trouble for Python-based projects to distribute >> extension binaries built with third-party toolchains. I suppose there >> are very few Python-based projects that do so, in or out of GNU. >> >> So your best bet is FS advocates who also use Python a lot, and <a href="http://c.l.py">c.l.py</a> >> is most likely where you'll find them. HTH > > Thanks. There are a few pages floating around that explain how to use > MinGW, but they all describe how to tweak distutils to invoke MinGW > rather than MSVC. That requires to have Python installed, so this is > not what I'm looking for. > > This comes the closest to what I need: > > <a href="http://docs.python.org/extending/windows.html#using-dlls-in-practice">http://docs.python.org/extending/windows.html#using-dlls-in-practice</a> > > although it uses MSVC. But "translation" to MinGW is simple. The > example indicates that the Python include directory and import library > are needed, even for such manual techniques... > > So it looks like having such extension as part of the standalone > installer is the only practical way that doesn't require a Python > installation. > </div>