I just tried to compile some extensions on Win XP with .NET 1.1 and Python 2.4c1 installed. It turns out that the distutils recognition logic for finding a suitable C compiler is not able to find the compiler by simply looking at the PATH, INCLUDE and LIB settings of the OS instead of poking around in the registry :-) Now since extensions for 2.4 will have to be built using the same compiler as Python itself (the one that comes with VC7.1 which is the same as the one in the freely downloadable .NET 1.1 SDK), I would suggest to make distutils aware of the compiler by looking on the PATH in case the registry doesn't have the VC7.1 entries. I think this would be a good patch candidate for 2.4.1 - not sure whether it's important enough to squeeze something into 2.4c2. What do you think ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 26 2004)
Python/Zope Consulting and Support ... http://www.egenix.com/ mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::