Nicolas Lehuen wrote:
This raise this issue : under Win32, the preferred way to build
mod_python is to run :
python setup.py.in <http://setup.py.in> bdist_wininst --install-script
win32_postinstall.py
This leaves no room to specify a MAX_LOCK definition override, but I
guess we could put it in setup.py, since extension modules can have
custome macro definitions.
My question is : should we keep on with ./configure ; make ; make
install or try to do everything in setup.py ?
As long as we can put setup.py in a Makefile. ;)
Seriously though, ./configure --help; ./configure; make; make install;
is just such second nature to me I never even thought of the alternative.
I'm still a little puzzled about the current setup.py though, because it
gets configuration information from config.status, which is generated by
./configure. I guess that's another story.
import this
"There should be one-- and preferably only one --obvious way to do it."
So if distutils can do the job, with the same functionality, and be
cross platform friendly then I'm all for it (but not in 3.2.0), even if
it means breaking my Makefile habit. It does not make sense to spend our
time maintaining 2 different build methods. (And it's a chance for me to
learn the distutils black magic).
Regards,
Jim
