I'm sorry that this is going to come out sounding like a flame, but it seems to me that there today only a few technical problems remaining with Python when built with mingw32.
If one of the people who has expressed such deep concern about this "msvcr71.dll" problem would simply install the Free tools and start putting patches on sourceforge, it's quite possible that for the next 2.4.x release the mingw32 "port" could be a first-rate one, and suitable for the uses that the posters in this thread have mentioned. Since mingw32 is Free (gpl and other licenses for tools, public domain libraries and copyrighted headers with "no restrictions for programs" built using the headers) anyone can install and use these tools and mingw creates no new problems with distribution of the resulting binary, whether the final product is Free or proprietary. (Admittedly I don't know anything about whether "win32all" builds under mingw32, and it's not clear whether binary compatibility with extensions built by microsoft compilers is an easy goal either) http://www.mingw.org/ Jeff
pgplhycX3JBjH.pgp
Description: PGP signature
-- http://mail.python.org/mailman/listinfo/python-list
