[Python-Dev] [win32] Killing MSVC's _alloca (original) (raw)

Gerhard Haering gerhard.haering@gmx.de
Sat, 5 Oct 2002 03:26:47 +0200

No, this can go in now. That's the point of my plan to submit several isolated patches. I don't want to fork a Python tree, work several months on it, and then submit one gigantic patch, that will probably never be applied because there are problems reviewing it.

> These will ultimately make it possible to build Python on win32 using the > autoconf/make toolchain.

I don't understand. How many Unix emulations on Windows do we need?

mingw is not a Unix emulation. It is the GNU Compiler suite targetting native Windows. The point is to be able to build Python on Windows with the autoconf toolchain. And without needing to buy Visual C++ just to do build Python or to do serious Python extension development on Windows.

We've already absorbed a sheer endless set of patches to make it work on CYGWIN. How does Mingw differ?

mingw produces native win32 executables. No emulation whatsoever.

> See http://python.org/sf/618791 > > I've assigned it to Guido for no good reason except being not sure > if Mark knows about autoconf/makesetup, which my patch touches. > > But I'd also be glad if anybody else applies it ;-)

Me too. I may reduce the priority.

The reason for setting a higher priority was that I hoped this could be applied rather sooner than later, as I hoped this wasn't a controversial patch.

-- Gerhard