Moore, Paul wrote:
From: Mark Hammond
Does the move to VC7 mean that we'll break this strategy with Python 2.4 distutils ?
Yes, unless we do as outlined in my mail.
I may be misunderstanding what is being discussed here, but I believe that with the move to VC7, you will need the following to build extensions compatible with both Python 2.3 and 2.4:
1. Installed copies of both Python 2.3 and 2.4. 2. EITHER MSVC 6 and 7 (both versions) OR mingw
But I am probably missing something, as once you have the 2 versions of Python installed, I don't see the value in using a single shared distutils, rather than the one that comes with each Python.
The latter would mean having to support 3-4 different distutils versions in your setup code. We already support 3-4 different Python versions (at Python and C level) and would like, if at all possible, to continue building all packages with one distutils version - the one in CVS which is the most up-to-date. That said, I think that including two wininst versions, one compiled with VC6, the other with VC7, would solve this problem nicely. You'd still have to have VC6/7 for compiling C extensions, but at least generating pure Python distutils wininst packages would remain possible. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Feb 05 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/
2004-01-23: Released mxODBC.Zope.DA 1.0.8 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::