From: David C. <da...@ar...> - 2009-10-02 06:07:38
|
Hi Andrew, Andrew Straw wrote: > Dear David, > > It certainly is of interest to me. When I get a little time (maybe this > weekend), I'd like to try it. Specifically, I'd like to setup a buildbot > that would automatically build and run the test suite with it. Along > those lines, is there any reason why it shouldn't work with Ubuntu Hardy > amd64 (8.04) and Python 2.5? Or should I try another distro? (I'll be > setting up a chroot.) > It should work on any distro. I have not tested this really hard yet, though - but it already works better for me than the current setupext.py (I may miss something, but the detection fails horribly on my machine, especially for libs not installed in /usr). There are some configurations which are not supported yet (wxpython < 2.8, tkagg, and win32 + mac os x backends), but it should be relatively easy to add support for it, except maybe for mac os x backend because of objective c because numscons does not handle objective C yet (my focus is windows ATM, but if supporting every configuration is a condition for the patch to be included, I am willing to work on it). > looks pretty unintrusive to me -- I can't see why it would hurt to > include it direct into MPL. The patch could be made smaller and more robust if I were allowed to do some basic refactoring to share configuration data between setup.py and setupscons.py: either fixing setup.py so that it uses a __main__ and does not execute the whole distutils dance at import time, or as I usually do in other projects, putting metadata in a separate file. cheers, David |