On Aug 2, 2007, at 7:33 AM, Stefan Behnel wrote:
Actually, in the *long* term, I rather see lxml in the Python stdlib,
including libxml2 and libxslt. :)
I'd actually rather not see it in the stdlib. I and others in the
Zope community are finding that keeping components separate does more
On Wed, Jul 18, 2007 at 12:22:26PM +0200, Jos Vos wrote:
On Wed, Jul 18, 2007 at 11:48:53AM +0200, Stefan Behnel wrote:
;) the recommended way to use libxml2 from Python is lxml.
Thanks, but if anyhow possible, I'd like to stick to something
that is available from stock RHEL5 and
Daniel Veillard wrote:
On Wed, Jul 18, 2007 at 12:22:26PM +0200, Jos Vos wrote:
On Wed, Jul 18, 2007 at 11:48:53AM +0200, Stefan Behnel wrote:
;) the recommended way to use libxml2 from Python is lxml.
Thanks, but if anyhow possible, I'd like to stick to something
that is available from
Hi,
What is the recommended way (in the libxml2 Python binding) to copy
a node and all of its children (but not its siblings!) from one
document to another document?
I tried (x is a node in the new document, y a node in the old document):
x.addChild(y)
Jos Vos wrote:
What is the recommended way (in the libxml2 Python binding) to copy
a node and all of its children (but not its siblings!) from one
document to another document?
;) the recommended way to use libxml2 from Python is lxml.
I tried (x is a node in the new document, y a node in
On Wed, Jul 18, 2007 at 11:48:53AM +0200, Stefan Behnel wrote:
;) the recommended way to use libxml2 from Python is lxml.
Thanks, but if anyhow possible, I'd like to stick to something
that is available from stock RHEL5 and python-lxml isn't included
there.
Ok, you want to copy, not move the
