Re: vlibxml2 and lxml

Hey,

I managed to get my code checked into the trunk line of lxml just now.  
I just checked in my old vlibxml2 tree under the trunk of lxml's trunk.

How do you want to co-ordinate the source tree changes?  Is there an 
automated build process that I should be aware of?  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.

What's the intent of having the branch vs the tag directories in the 
svn repository?  Are tags considered releases?

A couple notes about my vlibxml2 - there's a bug in the replaceNode 
method.  I'm not sure exactly what's going on but when I actually use 
the code in my 'real' project at work I get weird XML output.  I'll try 
to investigate tonight to see exactly what's going on.

so many questions, so little time...

vic

_______________________________________________
lxml-dev mailing list
lxml-dev <at> codespeak.net
http://codespeak.net/mailman/listinfo/lxml-dev