From: Andrew S. <str...@as...> - 2009-11-25 16:52:45
|
David Cournapeau wrote: > Andrew Straw wrote: > >> Michael Droettboom wrote: >> >>> I know it's been a while since you announced this, but I'm just >>> looking into this now. >>> >> Also, I got some ways in making the buildbot build with numscons, but >> I stopped at a bug where it looked like the matplotlib.tests.* modules >> were not getting installed: >> >> http://mpl-buildbot.code.astraw.com/builders/Ubuntu%208.04%2C%20Python%202.5%2C%20amd64%2C%20scons/builds/13/steps/test/logs/stdio >> >> >> > > I will look at it. I would like to get some kind of automated testing > for matplotlib on windows 64 (which is built using the numscons build), > so I have the incentive :) > I looked a little further, and it depends on the directory that the tests are run from -- if I manually log into the build slave, I can get the tests to run (in fact, one segfaults) if I try from a different working directory. Anyhow, now that I have a handle on it, I think I can probably get it working... Give me a couple days. win64 builds wold be great. > >> I haven't had a chance to debug this further, but I'm open to ideas. >> Also, this branch is building from a git repository (a mirror of >> David's which I can't clone normally, for some reason), for what it's >> worth. >> > > I don't know why I have those problems either. Do you think it would be > possible to just apply the patch suite to trunk in svn once we fix the > test issue ? Since the patches do not touch the existing source tree > (except for a few bugs on windows I can split up if required), it would > be more practical to have all this in svn. > As far as I'm concerned, that would be fine. Is PyMODINIT_FUNC pulled in from Python.h? Also, would you like svn commit access? That may just make things easier -- John, what do you think? I think we can trust David. :) -Andrew |