"Mark W. Alexander" wrote:
On Fri, 26 May 2000, M.-A. Lemburg wrote:
Well, e.g. mxDateTime was a package in the sense that you can unzip it directly in a directory on you PYTHONPATH. Only the "base" archive will have that property. The others are add-in archives which get unzipped on top of the "base" installation.
Hmm, thinking of it: would distutils allow recursive builds/installs ? Or must I add logic to figure out which parts of the cake are available to build/install and then setup a single setup.py file ?
It allows for nested packages, if that's what you mean. I didn't have much trouble backing a setup.py that did mxDateTime, mxTextTools, and mxTools. I don't see any problem with each having their own setup.py, IF you have (as you mentioned) a "core" package that provides the foundation for all the others.
It would probably be wise to have one setup.py file per ZIP archive. The ZIP archives have predefined content and the setup.py files could have this information hard-coded somewhere. I would have to move away from my current installation logic though (simply unzipping and then compiling in place). With distutils help this shouldn't be much of a problem though (I hope ;-). -- Marc-Andre Lemburg ______________________________________________________________________ Business: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/