I wont' be able to touch it until later this week, but I'll just branch the trunk and reorganize everything into one source tree if nobody really minds. There's a couple bugs I need to squash and a good bit of restructuring that I'd like to get done so that I can start using this XML library in my day job. :) As for the automated build, at work, I setup a build process which basically runs distutils, runs the testsuite and then emails the results. Alternately, we could overload the test runner to do some XML/HTML output a'la Cruise Control: http://cruisecontrol.sourceforge.net/. I'd really like to get some XML output generated when a test suite is completed - it would really make it easier to do stuff like a web status board. Anwyay - I'll concentrate getting the new file layout sorted out in a couple days. I'll probably mark the victree stuff as 'deprecated' or something. I'm not too interested in keeping it alive if etree does everything anyway. vic --- "Consequences, Schmonsequences, as long as I'm rich." -- Looney Tunes, Ali Baba Bunny (1957, Chuck Jones) On 13-Nov-04, at 04:04 AM, Martijn Faassen wrote:
Victor Ng wrote: [snip]
How do you want to co-ordinate the source tree changes? Is there an automated build process that I should be aware of?
We don't have an automated build process. I can setup an automated build if anyone is interested.
Would be interesting. I presume it'd try to compile and run the tests, and send some form of report?
Hm..I thought I saw tests in the vlibxml2 I downloaded before, but I cannot seem to find them now. Anyway, the testrunner, test.py, should pick up any tests called test_, typically placed in a 'tests' subpackage to the one being tested. Sorry about that - missed that when I copied files from my directory to codespeak's. You should see it now. I've cleaned up the tests a little so you'll see that the victree code has no tests around it - i had some bug in the tests so I just deleted them all. I'll resurrect them when it's fixed. :)
We'll need to discuss what to do about victree.py/etree.pyx anyway. You'll note that etree.pyx does have quite a few tests.
What about the source code reorganization issue I discussed? Right now we have two distribution directories, which is rather awkward.
Regards,
Martijn