Mailman 3 June 2008 - lxml - The Python XML Toolkit

[lxml-dev] lxml 2.0.7 released
by Stefan Behnel 24 Jun '08

24 Jun '08

Hi all, I just released lxml 2.0.7 to PyPI. This is a bug-and-convenience-fixes-only release for the stable 2.0 series. Changelog below. The C sources in this release were generated with Cython 0.9.8 and tested with Python 2.6 beta1. Have fun, Stefan 2.0.7 (2008-06-20) Features added * Pickling ElementTree objects in lxml.objectify. Bugs fixed * Descending dot-separated classes in CSS selectors were not resolved correctly. * ElementTree.parse() didn't handle target parser result. * Potential threading problem in XInclude. * Crash in Element class lookup classes when the __init__() method of the super class is not called from Python subclasses. Other changes * Non-ASCII characters in attribute values are no longer escaped on serialisation.

2 1

[lxml-dev] operator.delslice() not working with 2.1beta3
by Holger Joukl 23 Jun '08

23 Jun '08

Hi, I just realized that operator.delslice() does not work with 2.1beta3: >>> root = msg >>> root.a = [1,2,3,4] >>> import operator >>> operator.delslice(msg.a, 0, 4) Traceback (most recent call last): File "<stdin>", line 1, in ? TypeError: object doesn't support slice deletion >>> which worked in 2.0alpha >>> root = msg >>> root.a = [1,2,3,4] >>> import operator >>> operator.delslice(msg.a, 0, 4) >>> I suspect this was introduced with extended slicing. operator.getslice and operator.setslice still work, btw. Holger -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

3 3

[lxml-dev] Potential bug when using nth-child in CSSSelector
by John Evans 22 Jun '08

22 Jun '08

Hi All, I have observed some unexpected behavior with lxml -- I looked in the bug tracker and didn't see anything that seemed related to this. daedalus:~ john$ python Python 2.5.2 Stackless 3.1b3 060516 (python-2.52:61022, Feb 27 2008, 16:52:03) [GCC 4.0.1 (Apple Computer, Inc. build 5341)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from lxml.cssselect import CSSSelector >>> CSSSelector("div div:nth-child(5) div div div:nth-child(3) img").path "descendant-or-self::div/descendant::*[name() = 'div' and (position() = 5)]" >>> It looks like when you use the nth-child member in a CSSSelector it chops off the rest of the CSSSelector and does not process it when compiling it down to an xpath. Is this a bug or am I just doing something stupid? Thanks, - John

2 2

[lxml-dev] text of an etree Element
by Ofer Kalisky 19 Jun '08

19 Jun '08

Hi, When I access some node's text (node.text) I get only the first text value of it, for example, if the html is: <html><body>asdf<b>something</b>qwer</body></html> and "node" is the "<body>", then node.text retrieves asdf. if I use node.itertext(), I get [asdf, something, qwer], which is again, not what I want... is there a way to reach the other text of a node ("qwer")? _________________________________________________________________ Connect to the next generation of MSN Messenger http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=…

3 2

[lxml-dev] lxml with utf-8
by Daniel Jirku 18 Jun '08

18 Jun '08

hi.. i'm new to lxml but very interested to using it... i now have a problem. i want to add an element with an umlaut (non ascii character), so im using utf-8. but as soon as i run my pyhton script, i get the following error: File "lxml.etree.pyx", line 835, in lxml.etree._Element.text.__set__ (src/lxml/lxml.etree.c:9595) File "apihelpers.pxi", line 409, in lxml.etree._setNodeText (src/lxml/lxml.etree.c:28436) File "apihelpers.pxi", line 951, in lxml.etree._utf8 (src/lxml/lxml.etree.c:32423) AssertionError: All strings must be XML compatible: Unicode or ASCII, no NULL bytes My script looks like this... # -*- coding: utf-8 -*- .... parser = etree.XMLParser(encoding="utf-8") etree.set_default_parser(parser) # bad sign 'ö' badString = "blöm" root = etree.Element("neuIns") for i in range(5): tagAd = etree.SubElement(root, "ad", id=str(i)) foo = etree.SubElement(tagAd, "foo") foo.text = badString.encode("utf8") toStringValue = etree.tostring(root, encoding="utf-8", method="xml") writeToFile(toStringValue) -------- all the new parser set up and badString.enocde i just did to be shure everything is utf-8... without it it also doesn't work :) my setup is: python 2.5 pydev (eclipse) default encoding in eclipse is utf-8, also stdout encoding is utf-8 i found this in the mailing list (http://article.gmane.org/gmane.comp.python.lxml.devel/2320/match=assertione…), but i think it should be possible to write utf-8 strings to an xml with lxml?! what i'm doing wrong... hope you can help.. thanks in advance.. dani. -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

2 1

Re: [lxml-dev] Error from Variables in Extension Functions?
by Thomas Schraitle 12 Jun '08

12 Jun '08

Hi, > Thomas Schraitle wrote: > > lxml-2.0.6 > > [...] > > <xsl:variable name="content"> > > <xsl:apply-templates/> > > </xsl:variable> > > <A><xsl:value-of select="myns:mytext($content)"/></A> > > [...] > > XSLTApplyError: XPath evaluation returned no result. > > Thanks for the test case. lxml 2.1 gives me a NotImplementedError when trying > to convert the XSLT result tree fragment in "content" to a Python object. So > this is actually a missing feature. Could you file a feature request in > launchpad for handling XSLT result trees in XPath? Ok, done. See https://bugs.launchpad.net/lxml/+bug/239425 Tom

1 0

[lxml-dev] Error from Variables in Extension Functions?
by Thomas Schraitle 12 Jun '08

12 Jun '08

Hi, as I am trying to learn more of lxml simplicity, I stumpled over a strange behaviour that I couldn't explain. Probably it's only my wrong understanding. :) I've played with some extension functions and I could condense my problem to a small testcase. Maybe it's totally dumb and useless and only my wrong understanding. Well, let's see. :) I used the source code from lxml-2.0.6, compiled it and modified the file in lxml/tests/test_xslt.py. I added the following small test function: def test_extensions3(self): tree = self.parse('<a><b>B</b></a>') style = self.parse('''\ <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:myns="testns" exclude-result-prefixes="myns"> <xsl:template match="a"> <xsl:variable name="content"> <xsl:apply-templates/> </xsl:variable> <A><xsl:value-of select="myns:mytext($content)"/></A> </xsl:template> </xsl:stylesheet>''') def mytext(ctxt, values): return 'X' * len(values) namespace = etree.FunctionNamespace('testns') namespace['mytext'] = mytext result = tree.xslt(style) self.assertEquals(self._rootstring(result), _bytes('<A>X</A>')) Actually, the function test_extensions3() is derived from test_extensions2. The only difference is the variable content which is passed on to the extension function. I've expected an identical result like test_extensions2. From what I know, I think it is a common approach to collect the content in a variable and pass it on to other functions. I've ran the testcase like this: $ python test.py -vv lxml/tests/test_xslt.py Unfortunately it gives me this output: ====================================================================== ERROR: test_extensions3 (lxml.tests.test_xslt.ETreeXSLTTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/lib64/python2.5/unittest.py", line 260, in run testMethod() File "/local/repos/home:thomas-schraitle/python-lxml/lxml-2.0.6/src/lxml/tests/test_xslt.py", line 620, in test_extensions3 result = tree.xslt(style) File "lxml.etree.pyx", line 1732, in lxml.etree._ElementTree.xslt (src/lxml/lxml.etree.c:16290) File "xslt.pxi", line 457, in lxml.etree.XSLT.__call__ (src/lxml/lxml.etree.c:83016) XSLTApplyError: XPath evaluation returned no result. ---------------------------------------------------------------------- Ran 54 tests in 0.686s FAILED (errors=1) Any hints what I'm doing wrong? Thanks, Tom Used libraries: libxml2-2.6.31-3.1 libxslt-1.1.22-3.2

3 2

[lxml-dev] How to access XSLT Parameters Inside an Extension Function?
by Thomas Schraitle 10 Jun '08

10 Jun '08

Hi, while I'm constantly learning lxml, I came across a problem in one of my extension functions: Let's say I have a couple of parameters in my XSLT file. How can I access them in my extension function? I've looked into the documentation, mainly "Extension functions for XPath and XSLT", however I couldn't find anything about it, nor an example for this specific case. Perhaps I just overlooked it. Can someone give me a hint where to look? Or maybe a small example would be greatly appreciated. Thanks, Tom -- Thomas Schraitle

2 6

Re: [lxml-dev] Patch for xpathgrep.py
by Thomas Schraitle 10 Jun '08

10 Jun '08

Hi Stefan, > [...] > > To improve it a bit, I've created a humble patch against xpathgrep.py. > > I've > > looked at it and I missed a namespace option. Well, here it is. See the > > attached patch. Hope it's ok, feel free to adapt it to your needs. > > I considered using ETXPath() instead of plain XPath() for that script, so > that you can say "//{ns}stuff". But I think your patch makes sense as well > and may mean less typing/c&p on the cmd line. I'll enable both then. Ahh, I forgot about the Clark notation. Good to know, thanks! I'm so get used to the prefix notation. By the way, I think there is a small error in my patch: The variable namespaces isn't correctly initialized. There should be a "parser.set_defaults(namespaces=[])" before the "parser.add_option("-N", "--ns", ...)" line. To spread the word about lxml and xpathgrep.py: I've wrote a small article here: http://lizards.opensuse.org/2008/06/09/query-your-xml-with-xpathgreppy/ :-) Thanks, Tom

3 6

Re: [lxml-dev] xpath comparison
by Olivier Collioud 10 Jun '08

10 Jun '08

Hello. > Please report back if any of the above approaches worked better for you. Finally I choose to first collect SREF and MREF elements values from the first XML file in a dictionary/set structure (to factorise and avoid duplicates) and then loop over it for each SYMBOL found in the second XML file. This solution is at least 10 times faster than the previous one and is fast enough. Thank you. Olivier. ------ World Intellectual Property Organization Disclaimer: This electronic message may contain privileged, confidential and copyright protected information. If you have received this e-mail by mistake, please immediately notify the sender and delete this e-mail and all its attachments. Please ensure all e-mail attachments are scanned for viruses prior to opening or using.

1 0