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