|
From: <kon...@la...> - 2006-01-23 17:27:44
|
On Jan 23, 2006, at 18:07, Andrew Straw wrote: > Let's say you wanted to have Scientific 2.4.2 depend on Numeric 23.5. > You'd make sure the call to setup() (which is now imported from > setuptools, not distutils.core) included the following: ... OK, that looks sophisticated enough to me :-) Since setuptools keeps track of dependencies, it should be able to =20 provide on demand a list of all include file directories for all =20 packages on which the current build procedure depends, directly or =20 indirectly. To stay within my example, a package that depends on =20 ScientificPython, which in turn depends on Numeric, should be able to =20= get, with a single call, the include directories for *both* =20 ScientificPython and Numeric. Assuming such a mechanism exists, and is also implemented in plain =20 distutils (returning just the standard installation paths), then =20 personally I wouldn't care where header files are, because there is a =20= straightforward way to obtain that information. However, that is not what is currently being discussed for numpy, =20 unless I missed something. What is being discussed is an arrangement =20 that requires the setup.py of every package to reconstruct the =20 dependency tree and figure out where each package in the dependency =20 tree keeps its header files. There is something else that I don't understand. If egg installation =20 uses setup from setuptools instead of distutils, it should be trivial =20= for the setup function from setuptools to implement install_headers =20 in a way that suits its need. So why request that numpy (and other =20 packages) adapt to setuptools, creating compatibility issues with =20 standard distutils, rather than modify setuptools and have it work =20 automatically for all packages? Konrad. -- --------------------------------------------------------------------- Konrad Hinsen Laboratoire L=E9on Brillouin, CEA Saclay, 91191 Gif-sur-Yvette Cedex, France Tel.: +33-1 69 08 79 25 Fax: +33-1 69 08 82 61 E-Mail: kh...@ce... --------------------------------------------------------------------- |