Hey, I split off a discussion about source code layout into a separate thread, but I'll answer these ones here: 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 think we should be able to merge your setup.py with the one in lxml already. Mine does it best to shut up gcc about all kinds of warnings in Pyrex generated code. This is not very portable beyond gcc; we need to work out eventually how to pass along different options with other compilers such as on Windows. The Makefile in lxml I believe I took more or less from the Zope 3 project. Most relevant are 'make' and 'make test'.
I'm on an OSX machine so I don't have access to valgrind - I was wondering if I can see build results that show that memory leaks are not actually happening.
No automated build process. The thing I do is: valgrind --tool=memcheck --suppressions=valgrind-python.supp python2.3 test.py if we get vlibxml2 integrated into lxml's 'src' directory the tests should be picked up automatically and I can mail a report to the list. 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. This is an example: http://codespeak.net/svn/lxml/trunk/src/lxml/tests/ Regards, Martijn