Mailman 3 February 2010 - lxml - The Python XML Toolkit

[lxml-dev] Copying children including text nodes
by Martin Aspeli 08 Feb '10

08 Feb '10

Hi, I have two trees that were parsed with the HTML parser. The source tree is: <html> <head> <body> Foo <p>Bar</p> Baz </body> </html> The target is: <html> <head> <body> <div id="target">Placeholder</div> </body> </html> Now, I want to replace the whole of <div id="target"> tag (so, the tag and its children) with the *contents* of the <body> tag in the source tree. I obviously don't want the body tag itself. Performance is important. Also, I don't care about the source tree after I'm done, so if "moving" rather than copying makes things faster/easier, that's OK. What's the best way to do this? My naive approach was to do this: sourceBody = source.find('body') for sourceBodyChild in sourceBody: targetPlaceholder.addnext(sourceBodyChild) targetPlaceholder.getparent().remove(targetPlaceholder) However, this loses the text ("Foo"). I guess this is one case where dealing with text nodes explicitly would actually be better. :) Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book

2 1

[lxml-dev] Typo in exception message
by Antti Kaihola 08 Feb '10

08 Feb '10

Hi, I'm catching exceptions from cssselect and my code needs to make decisions based on not only exception classes but also the particular exception messages. The word "pseudo" is mistyped as "psuedo" in four different exceptions. Are these typos going to be kept unchanged for good, or should my code be prepared to match a corrected version as well? The same typo seems to occur on the lxml web pages as well, by the way. Regards, Antti Kaihola Espoo, Finland

2 1

[lxml-dev] Get the xml-stylesheet processing instruction
by David Chandek-Stark 06 Feb '10

06 Feb '10

Hi, I had a hard time tracking this info down (only figured out after reading the thread at http://codespeak.net/pipermail/lxml-dev/2006-September/001903.html), so posted a recipe: http://fragmentsofcode.wordpress.com/2010/02/05/get-the-xml-stylesheet-proc… Feel free to use or copy for any purpose. Thanks, David -- David Chandek-Stark dchandekstark (at) gmail (dot) com

3 2

[lxml-dev] ElementTree 1.3a xpath position broken?
by Richard Baron Penman 02 Feb '10

02 Feb '10

hello, I am after xpath support for an application running on Google App Engine, which unfortunately rules out lxml. According to this document (http://effbot.org/zone/element-xpath.htm) the development version of ElementTree 1.3a has additional support for xpath, which covers my use cases. >From my tests I found attributes and child nodes work: >>> from elementtree import ElementTree >>> tree = ElementTree.fromstring('<a><b></b><b><c class="test"></c></b></a>') >>> print list(tree.findall('.//*[@class="test"]')) [<Element 'c' at b7caa0cc>] >>> print list(tree.findall('.//b[c]')) [<Element 'b' at b7caa08c>] However tag positions appear to be broken: >>> print list(tree.findall('.//b[1]')) # should return b element [] Have I missed something? Suggestions? regards, Richard

2 5

[lxml-dev] exslt functions in xpath expressions
by Dirk Rothe 01 Feb '10

01 Feb '10

During XPath Evaluations in XSL-Transformations it's possible to use Stuff from http://www.exslt.org/ (so [5] does indeed match the <a> element). During XPath Evaluations its only possible to use standard XPath/XSLT Functions. Is there a chance to enable the functions from exslt for lxml XPath evaluations as well? ========================================================= In [1]: from lxml import etree In [2]: from StringIO import StringIO In [3]: tree = etree.parse(StringIO('<a b="12"/>')) In [4]: print tree.xpath('/a[@b=concat("1","2")]') [<Element a at 2dbfbd0>] In [5]: print tree.xpath('/a[@b=str:split("12 34")]') [] ========================================================= --dirk

2 5