Actually - I started working on the vlibxml2 stuff prior to the announcement of the lxml project. I was also negotiating an agreement at my workplace so that I can work on the XML library during office hours as long as the license was a BSD license. All of that has been sorted out now - and I've really got no time to setup everything you folks have already done at codespeak. I'd really like to keep vlibxml2 and lxml separate. This is mostly for technical reasons as the libxml2 library has some really quirky behavior in it's API. I'd actually like to rewrite a lot of the vlibxml2 code now that I understand the idioms in libxml2 a little better. I guess you really do need to do it 87 times before you get it right. :) So - in the interest of playing nice with everyone - can I get checkin privs to the lxml SVN repository? vic On 9-Nov-04, at 04:20 AM, Martijn Faassen wrote:
Hi there,
Back from my honeymoon I see that Victor has released vlibxml2. Cool! Thanks Victor!
I hope that we can still converge it all into a single package -- vlibxml2 aims to do a fairly low-level straightforward mapping for parts of the libxml2 API, as I understand it, while lxml aims to raises the level of the API. The approaches don't need to exclude each other however and pooling them together could help both.
Victor, I'm curious about the reasons why you didn't use the existing lxml infrastructure (svn, mailinglist, etc) to do what you've been doing? Were you under the impression that what you were aiming at is outside the scope of lxml? I think people would prefer there not be two pyrex based wrappers for libxml2. Is there anything we can change with lxml so that you'd be happy to merge the projects?
I see that Victor changed his license from GPL to BSD (though the README.txt of the 0.1.177 release still says it's GPL-ed). That's great; it means no matter what happens with lxml/vlibxml2 convergence, lxml can hopefully at least 'borrow' the memory management code from vlibxml2. Thanks again Victor!
Regards,
Martijn