Mailman 3 November 2009 - lxml - The Python XML Toolkit

[lxml-dev] lxml has its page on launchpad
by Stefan Behnel April 11, 2023

April 11, 2023

Hi all, I added the lxml project to launchpad, the Ubuntu Bug-Tracker. It also has a FAQ engine and a couple of other goodies. https://launchpad.net/lxml It's easy to sign up for launchpad, BTW, no 90%-footnotes-contract. Have fun, Stefan

9 9

[lxml-dev] Checking whether a node is a comment/element
by Geoffrey Sneddon April 10, 2023

April 10, 2023

Hi, What's the best way to check whether a given node is a comment or an element? For the former, I'm currently using isinstance(node, etree._Comment), which is rather obviously sub-optimal. -- Geoffrey Sneddon <http://gsnedders.com/>

6 6

[lxml-dev] Reparenting a node
by Lawrence Oluyede Jan. 30, 2023

Jan. 30, 2023

I have a doc A and a doc B, I'd like to put a node extracted from A in the document B but I always get a ValueError: ValueError: Element is not a child of this node. I didn't find any "setparent" in the API. How can I do this? -- Lawrence, oluyede.org - neropercaso.it "It is difficult to get a man to understand something when his salary depends on not understanding it" - Upton Sinclair

3 2

[lxml-dev] lxml 2.0.5 released
by Stefan Behnel Jan. 11, 2023

Jan. 11, 2023

Hi all, lxml 2.0.5 is on PyPI. This is a bug-fix-only release of the stable 2.0 series. Have fun, Stefan 2.0.5 (2008-05-01) Bugs fixed * Resolving to a filename in custom resolvers didn't work. * lxml did not honour libxslt's second error state "STOPPED", which let some XSLT errors pass silently. * Memory leak in Schematron with libxml2 >= 2.6.31.

3 4

[lxml-dev] Building LXML Trunk
by Sidnei da Silva Aug. 31, 2022

Aug. 31, 2022

Hi, I've tried to build lxml from trunk today, on Win32. Got the following error: src\lxml\etree.c(880) : error C2059: syntax error : ')' src\lxml\etree.c(881) : error C2059: syntax error : ')' src\lxml\etree.c(882) : error C2059: syntax error : ')' src\lxml\etree.c(883) : error C2059: syntax error : ')' Any clue? Smells like a Pyrex issue? -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

4 4

[lxml-dev] confusing xpath performance characteristics
by jholg＠gmx.de Aug. 24, 2012

Aug. 24, 2012

Hi, I ran into some performance characteristics of lxml/libxml2 xpath that I find rather confusing: I try to find the @type attribute of a certain element in an XML Schema (which contains lots of complexType definitions with lots of elements in them; unfortunately I can't post the schema): >>> timeit.Timer(stmt="""xpath(schema)""", setup="""from lxml import etree, objectify; schema=etree.parse('NDM.xsd').getroot(); xpath = etree.XPath('//xs:element[@name="equity"]/@type', namespaces={'xs': 'http://www.w3.org/2001/XMLSchema'})""").repeat(number=10) [0.095885038375854492, 0.096823930740356445, 0.096174955368041992] So I think I'm being smart and give a little more path information - reckoning that this should *improve* performance: >>> timeit.Timer(stmt="""xpath(schema)""", setup="""from lxml import etree, objectify; schema=etree.parse('NDM.xsd').getroot(); xpath = etree.XPath('/xs:schema//xs:element[@name="equity"]/@type', namespaces={'xs': 'http://www.w3.org/2001/XMLSchema'})""").repeat(number=10) [0.1770780086517334, 0.1775970458984375, 0.17748594284057617] Hm. Performance degrades slightly. I'm adding even more of the path to where my desired elements live in the schema: >>> timeit.Timer(stmt="""xpath(schema)""", setup="""from lxml import etree, objectify; schema=etree.parse('xsd/NDM.xsd').getroot(); xpath = etree.XPath('/xs:schema/xs:complexType//xs:element[@name="equity"]/@type', namespaces={'xs': 'http://www.w3.org/2001/XMLSchema'})""").repeat(number=10) [103.79744100570679, 103.83671712875366, 103.61817717552185] What??? >>> timeit.Timer(stmt="""xpath(schema)""", setup="""from lxml import etree, objectify; schema=etree.parse('/ae/data/pydev/hjoukl/NDM/SVN_CO/TRUNK/ndm/reference/xsd/NDM.xsd').getroot(); xpath = etree.XPath('/xs:schema/xs:complexType/*/xs:element[@name="equity"]/@type', namespaces={'xs': 'http://www.w3.org/2001/XMLSchema'})""").repeat(number=10) [0.044407129287719727, 0.044126987457275391, 0.044229030609130859] >>> Ok, this version's better than my naive approach, which seems logical to me. But why would '/xs:schema/xs:complexType//xs:element[@name="equity"]/@type' perform drastically slower than '/xs:schema/xs:complexType//xs:element[@name="equity"]/@type' ? libxml2 problem? Running the same xpaths in Oxygen I don't notice performance differences (can't profile this). Holger -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

2 5

[lxml-dev] Evaluate XSLT directives inside custom XSLT extension elements
by Marat Dakota Jan. 25, 2010

Jan. 25, 2010

Hi, I have a problem I couldn't find the way to solve. Sadly if it's not possible. That's the code from XSLT extensions tutorial: <xsl:template match="*"> <my:python-extension> <some-content /> </my:python-extension> </xsl:template> Everything's working cool, but I need a bit more: <xsl:template match="*"> <my:python-extension> <something><xsl:attribute name="test"><xsl:value-of select="111" /></xsl:attribute></something> </my:python-extension> </xsl:template> Let's assume that's my execute function's signature: execute(self, context, self_node, input_node, output_parent) When it's started by XSLT processor, self_node contains <something> tag with <xsl:attribute> and <xsl:value-of> tags inside it. What should I do to ask XSLT processor to evaluate it? I need to make self_node containing <something test="111" />. And even more. What if my XSLT file looks like: <xsl:template match="*"> <my:python-extension> <something> <xsl:attribute name="test"><xsl:value-of select="111" /></xsl:attribute> <my:python-extension> <xsl:attribute name="test2"><xsl:value-of select="222" /></xsl:attribute> </my:python-extension> </something> </my:python-extension> </xsl:template> I need to have execute function called for deepest <my:python-extension> first, I need to evaluate <xsl:attribute> inside it to have <my:python-extension test2="222">... And to process the rest <my:python-extension> having the result of processed <my:python-extension test2="222"> and all XSLT instructions inside. Is there a way to do it? Or maybe there is some other way to get such possibilities? Thanks. -- Marat

2 17

[lxml-dev] better schematron support
by jholg＠gmx.de Dec. 22, 2009

Dec. 22, 2009

Hi, schematron support in lxml is currently a second-class citizen due to libxml2 restrictions, see e.g. http://mail.gnome.org/archives/xml/2007-August/msg00016.html where Stefan commented on error reporting deficiencies or http://mail.gnome.org/archives/xml/2009-September/msg00022.html where Daniel of libxml2 fame comments on a feature request to support schematron embedded in XML Schema, basically stating that the implementation is incomplete. However, there is a pure-XSLT implementation of the now-ISO-standardized schematron by its inventor (and editor of the standard) Rick Jelliffe, the so-called skeleton implementation: http://www.schematron.com/ (Daniel also mentions this in his comment) Basically, the "skeleton" toolchain creates an xslt that is used for validation. Indeed, schematron itself is just a well-defined way of using xslt for validation, which I was looking into but really wasn't aware that schematron does this exactly. The "skeleton" implementation is available in both xslt 1 and 2 notions. The toolchain steps are (taken from www.schematron.com, modifications by me) 0) [Extract from XML Schema/RelaxNG schema)] 1) Process inclusions 2) Process abstract patterns 3) Compile the schema 4) Validate which translates to xsltproc XSD2Schtrn.xsl XMLSchema.xsd > theSchema.sch or xsltproc RNG2Schtrn.xsl RelaxNGSchema.rng > theSchema.sch xsltproc iso_dsdl_include.xsl theSchema.sch > theSchema1.sch xsltproc iso_abstract_expand.xsl theSchema1.sch > theSchema2.sch xsltproc iso_svrl_for_xsltn.xsl theSchema2.sch > theSchema.xsl xsltproc theSchema.xsl myDocument.xml > myResult.xml Enter libxslt aka lxml's xslt capabilities: It looks pretty easy to integrate this xslt-based toolchain into lxml, effectively enabling full ISO schematron support. I suggest complementing the current lxml schematron support using this approach: - add the necessary stylesheets (extraction and skeleton implementation) to the lxml codebase - add a convenient API to support xslt-based schematron validation to lxml that - hides toolchain steps, at least in default mode - fits in with the current validators' API - provides support for the parameters used for the separate toolchain steps And finally: Maybe somebody has already done this with lxml + schematron. Care to step forward? Any Comments? Holger -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser

2 19

[lxml-dev] Critical crashes on Windows under high load
by Martin Aspeli Dec. 5, 2009

Dec. 5, 2009

Hi folks, We have an incredibly frustrating, show-stopping problem using lxml (under Deliverance, in front of a repoze.zope2 pipeline serving up a Plone site) on Windows. Under high load, the Python process crashes. There is no traceback in the log, so I can't identify where it actually happens, but we get a Windows error dialogue saying python.exe (or pythonservice.exe if running as a Windows service) has crashed in etree.pyd (at some binary address, no line numbers or function references). The Deliverance (0.3/trunk) rules use fairly complex xpath expressions. We're trying to simplify these, but there's nothing obviously wrong, and in any case it shouldn't crash. We've tried to run both multi-threaded and single-threaded 'paster' processes: the problem happens with both. I did read somewhere that it's possible to build a single-threaded lxml egg (?), but I haven't found one. We would be incredibly grateful for any help with (a) debugging and (b) resolving this. At present, we're having to fight a lot of nervousness regarding the production-worthiness of our Deliverance/lxml based solution, which is rather unfortunate. :-( Cheers, Martin

2 6

[lxml-dev] XPath optimization troubles.
by John Krukoff Nov. 27, 2009

Nov. 27, 2009

Hello, I expect this is properly a libxml2 question, but it's weird enough I wanted to check here first to make sure that lxml isn't effecting the results. I have equivalent XPath expressions, one using prefixes to do the selection, and one using namespace-uri to do the check. The namespace-uri version consistently runs 2-3x faster on a range of test data, and I have no idea why. Here's the prefix version: > '//@gizmo:*/parent::*[ not( self::gizmo:* ) ]' And here's the namespace-uri version: > '//@*[ namespace-uri( ) = "%(gizmo)s" ]/parent::*[ namespace-uri( ) != "%(gizmo)s" ]' % namespaces I'm running these as compiled expressions using etree.XPath( ..., namespaces = namespaces ), if that makes a difference. Any hints? Or a faster XPath to do the same thing for the ambitiously bored? -- John Krukoff <jkrukoff(a)ltgc.com> Land Title Guarantee Company

2 2

[lxml-dev] Installing on Mac OS X 10.6.2: "lipo: can't figure out the architecture type of"
by Esben Bugge Nov. 25, 2009

Nov. 25, 2009

I have tried to install lxml on Mac OS X 10.6.2 using both sudo python setup.py build --static-deps and sudo STATIC_DEPS=true easy_install lxml In both cases I get lipo: can't figure out the architecture type of: /var/tmp//ccdcpY3e.out make[2]: *** [SAX.lo] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Exception: Command "make" returned code 2 What can I do to resolve this error?

2 3

[lxml-dev] elementtree as a hierarchical object tree
by cgnmm Nov. 24, 2009

Nov. 24, 2009

Hi, I'm new of lxml and XML programming. I would to use etree as a hierarchical object tree: every node element should have a property associated to an object. >>> import lxml.etree as etree >>> element=etree.fromstring('<TAG>some text</TAG>') >>> element.text="a string" that's all ok, but: >>> element.text={'a':'real', 'python':'object'} TypeError: Argument must be string or unicode. OK, the property name is "text" so some text is expected! My question is: if write a custom element with a property called "object", may I store inside it a reference to an object?

2 1

[lxml-dev] Why can't I turn all xpath node types into string?
by Kevin Ar18 Nov. 24, 2009

Nov. 24, 2009

XML defines several node types that get returned by XPATH: http://www.w3.org/TR/xpath#data-model When I use the xpath feature in lxml and then try to read out the data, it won't work for certain node types. How can I get a string version of all node types? Examples follow. The following works: Domain/HTML: http://www.citiesxl.com/ XPATH: //div//a from lxml import etree self.xpath_list = self.tree.xpath(xpath) for entry in self.xpath_list: tmp = "" try: tmp = etree.tostring(entry) except: tmp = str(entry) print tmp In this example, xpath_list is of type: <class 'lxml.etree._Element'> The etree.tostring() function works for this type. The following will NOT work for etree.tostring() XPATH: //div//a/attribute::href It says it can't handle the type or something. In this case, xpath_list is of type: <class 'lxml.etree._ElementStringResult'> or something like that (I forget the actual type). The str() function will work on this one. The following will NOT work at all using either str() or etree.tostring() XPATH: //self::text() One of the types is: <type 'lxml.etree._ElementUnicodeResult'> and I get this error: UnicodeEncodeError: 'ascii' codec can't encode character u'\xa0' in position 38: ordinal not in range(128) Is there an lxml function that will convert all types to strings properly instead of trying to use this try/except hack to handle all the types? _________________________________________________________________ Bing brings you maps, menus, and reviews organized in one place. http://www.bing.com/search?q=restaurants&form=MFESRP&publ=WLHMTAG&crea=TEXT…

2 1

[lxml-dev] lxml 2.2.4 for Python 2.6
by srijit＠aim.com Nov. 24, 2009

Nov. 24, 2009

Is there any reason why lxml-2.2.4-py2.6-win32.egg or lxml-2.2.4.win32-py2.6.exe is not available in http://pypi.python.org/pypi/lxml/2.2.4? Best regards, /Srijit

3 2

Re: [lxml-dev] lxml slower than ElementTree?
by Stefan Behnel Nov. 24, 2009

Nov. 24, 2009

Hi, John Machin, 24.11.2009 14:00: > Thanks for your response, Stefan. You're welcome. > On 24/11/2009 7:48 PM, Stefan Behnel wrote: >> In general, ET can't compete with lxml.etree, whereas cET can, especially >> when you stay with code that supports both ET and lxml.etree. > > As it stands, the code tries to import xml.etree.cElementTree, then > cElementTree, then ElementTree. I plan to allow an override option, > where the caller can import any minimal-ET-subset-compliant module (e.g. > lxml) and pass it in. The mentioned speed comparison was using cET. >> - lxml parses much faster from file names than from open file(-like) >> objects, especially multi-threaded. ET handles them exactly the same. > > The MS Excel 2007 file format is a ZIP file containing compressed XML > documents. Hence one ends up parsing file-like objects. Sure, I expected something like that. The thing is just that parsing from file-like object from lxml means that it needs to walk all the way up the Python stack to look up and call the object's .read() method for each chunk of data, which then builds and returns a new Python string object. Parsing from a file path implies straight calls to C's file reading function, which works completely outside of the GIL. So there is a pretty huge performance penalty for file-like objects. This penalty applies to (c)ET as well, though, so that's not a reason for lxml to be slower than them. > For better or worse, ET comes with Python. Design goal was to avoid > requiring Nth party modules where appropriate I totally understand that design goal. Being in the stdlib is clearly a major advantage of ET. >> - ET creates the tree as Python objects once and for all, lxml creates >> Python proxies only at request. > > I acknowledge that ET may start swapping much sooner than lxml That's not what I was referring to, though. It's ok to call ET an elephant, but cET is actually *very* memory friendly. I meant to say that lxml.etree implies a performance penalty if you access many elements in the tree, where cET can just return their reference. The penalty is not large, but it's certainly worth being a bit more selective when walking the tree and searching elements. That's what XPath and getiterator(tagname) are great for. >> - Tree iteration using getiterator() in lxml.etree is much faster than in >> cET, and also much, much faster than using .find(). This strikes even >> more >> when searching specific tags, because fewer proxies have to be created. >> (c)ET doesn't show a difference here. > > A base class provides a controller method that uses > getiterator(tag=None) and a mapping from tags to methods. Each type of > document (about 5 types) has a subclass. I would expect that to be pretty fast on cET. For lxml.etree, however, it might still be faster to traverse the document independently for each interesting tag name - as long as the document fits into memory completely, and as long as the methods are independent from each other. The benefit certainly depends on the ratio of interesting versus ignored elements in the traversal, but given that lxml's tight traversal loop is easily an order of magnitude faster than even cET, being selective can really turn the vane here. > The area where heavy lifting is required is the worksheet document, > which contains cell elements as children of row elements. Max 2**20 rows > and max 2**14 cells per row. If iterparse is available, a specialised > controller method is used; it uses iterparse to iterate over row > elements (only "end" events), clearing each row as it is finished. This > should solve most of the memory problem for [c]ET. Extending this to > clear the root element (i.e. avoid leaving empty row elements lying > about) is a possibility. Too bad that a) lxml's iterparse() is slightly slower than the one in cET and b) clearing the root element doesn't work in lxml.etree I guess a) is where your initial comment mainly originated from. Regarding b), getting your hands at the root element in (c)ET would require you to also accept 'start' events, which usually results in such a huge performance drop for larger documents that it's almost always better to just leave the dead elements around instead. Also note that lxml.etree would allow you to drop them during the iteration by removing the preceding siblings of the current row element through their common parent element. So you can have the cake and eat it, too. :) Stefan

1 0

[lxml-dev] lxml slower than ElementTree?
by Chris Withers Nov. 24, 2009

Nov. 24, 2009

Background: John maintains xlrd, the python package for reading Excel files, and is looking to support Microsoft's newer xml based format... John Machin wrote: <snip> > Note that it needs an ElementTree implementation (supplied with more > recent Pythons), and tries to find one in various places. Limited > testing with lxml gave identical results, but slightly slower, so you > could try that instead if you wanted to (would require fiddling with > imports in xlsxrd.py) That surprised me. Would anyone here be interested in taking a look at John's code to see what's tripping up lxml and causing it to be slower? cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk

2 1

[lxml-dev] lxml Win32 egg for Python 2.6
by Celvin Nov. 23, 2009

Nov. 23, 2009

Hi, I just went to my local cheese shop to upgrade lxml for Python 2.6 but noticed that there are only lxml 2.2.4 / Python 2.6 packages for AMD64 - is this intentional or a mere oversight? Cheers, Celvin

2 1

[lxml-dev] smart_strings
by Nicolas Delaby Nov. 23, 2009

Nov. 23, 2009

Hi, I would like to know if exists a way to reach an attribute name with an xpath result from _ElementStringResult instance. I see that we can reach is parent, but i need to know to which attribute this result belong, without parsing xpath expression with regex or something similar. root = etree.XML('<root><a a="aaa">TEXT</a></root>') result = root.xpath('/root/a/attribute::a')[0] assert result.is_attribute result.getparent().???? Regards, Nicolas -- Nicolas Delaby Nexedi: Consulting and Development of Libre / Open Source Software http://www.nexedi.com/

2 2

[lxml-dev] etree not printing pretty :(
by Martin Seiler Nov. 19, 2009

Nov. 19, 2009

Hi all, I am rather new to python and lxml and I wonder about the output of my tree. I add an Element, which contains some childs to a tree. When I write the output everything is in pretty print, but the elements I appended. They show up in one line. Here is a snippet of my code: > eggs = et.fromstring(xmltransformed) > for each in eggs: > if each.tag == "someElement": > > each.append(anotherElement) > > else: > pass > > > et.ElementTree(element=eggs).write(xmlout, pretty_print=True) When I open the file in firefox its formated all right, but when I view the code 'anotherElement' with all its childs is just one line... what am I doing wrong here? python: 2.6 python-lxml: 2.1.5-1ubuntu2 OS: Ubuntu 9.04 Thanks for you help! Cheers, martin

2 1

[lxml-dev] Python 2.6 Win-32 binary?
by Mike Naglee Nov. 18, 2009

Nov. 18, 2009

Hey folks, Am I just missing something or is there no Python 2.6 Win32 binary for lxml? Thanks, and have an interesting day! Mike

1 0

Re: [lxml-dev] etree Parser corrupting HTML
by Stefan Behnel Nov. 16, 2009

Nov. 16, 2009

Clif Swiggett, 16.11.2009 17:29: > Thanks for the tips to tighten up my code. > Do you have any suggestions for how best to detect whether a source file > is html or xml? I'm harvesting arbitrary files off the web ... You can either pass it into the XML parser and fall back to the HTML parser if that fails (which it most likely will for the large majority of HTML files), or, if you expect more HTML pages than XML pages, you can read the page into a string and search for the XHTML namespace before passing it into the parser. If you want to parse arbitrary web pages, you will likely end up using some kind of parser cascade anyway to make sure you get the best conformance and speed in the normal cases and the best error recovery in the pathological cases. Remember that lxml's parser is very fast, so it's ok to parse things multiple times with different parser configurations. Stefan

1 0

Re: [lxml-dev] inconsistency in the text nodes?
by Hervé Cauwelier Nov. 16, 2009

Nov. 16, 2009

On 16/11/2009 10:18, Stefan Behnel wrote: > > Hervé Cauwelier, 16.11.2009 10:07: >> I inherit from the Python unicode class, and wrap _Element*Result's >> parent in my own element class. > > That doesn't tell me why you would want to instantiate them yourself. It's because of the first test case where I test the construction of my own instances. I give an instance of text result without using XPath (which is tested in another test case). There's a factory function but it's not exposed to the Python level. Is it just because Cython requires variable initialization that these are declared in _ElementUnicodeResult but not in _ElementStringResult? I didn't noticed at first glance that _ElementStringResult is pure Python. I'm not familiar with Cython. Hervé

2 1

[lxml-dev] problem with etree.tostring and special characters inxml-text-attributes
by SCHLÖGL Thomas Nov. 16, 2009

Nov. 16, 2009

Hi, I have a problem with the replacement of special characters (xml-entities) in xml-text-properties of the etree.tostring method: After etree.tostring the characters &,<,> are replaced with & < > but ' and " remain in the text-properties. e.g.: <Property Name="Value">final_delim=end, record_delim='\n', delim='|', quote=double</Property> But I need: <Property Name="Value">final_delim=end, record_delim='\n', delim='|', quote=double</Property> I wrote a method that iterates through all text properties after the tostring-method and replaces ' and " of this text-properties in the serialized string, but with large xml-files this consumes a lot of time. Does anybody have a better solution? Kind Regards, Thomas Ing. Thomas Schlögl 4266-UGG3C1 / CFO Datawarehouse Core Solutions Member of the Crossfunctions-Team UniCredit Global Information Services S.p.A. (UGIS S.p.A.) Zweigniederlassung Österreich Nordbergstrasse 13 A-1090 Vienna Room: TZB-6.18 Tel: +43 1 71730 50499 Mobile: - mailto:thomas.schloegl@wave-solutions.com <mailto:anton.wazin@wave-solutions.com>

2 1

[lxml-dev] FW: problem with etree.tostring and special characters inxml-text-attributes
by SCHLÖGL Thomas Nov. 16, 2009

Nov. 16, 2009

Isn't there anybody who can give a comment to my question below (e.q. you're too stupid for lxml) ? Regards, Thomas From: SCHLÖGL Thomas Sent: Monday, November 09, 2009 4:20 PM To: 'lxml-dev(a)codespeak.net' Subject: problem with etree.tostring and special characters inxml-text-attributes Hi, I have a problem with the replacement of special characters (xml-entities) in xml-text-properties of the etree.tostring method: After etree.tostring the characters &,<,> are replaced with & < > but ' and " remain in the text-properties. e.g.: <Property Name="Value">final_delim=end, record_delim='\n', delim='|', quote=double</Property> But I need: <Property Name="Value">final_delim=end, record_delim='\n', delim='|', quote=double</Property> I wrote a method that iterates through all text properties after the tostring-method and replaces ' and " of this text-properties in the serialized string, but with large xml-files this consumes a lot of time. Does anybody have a better solution? Kind Regards, Thomas Ing. Thomas Schlögl 4266-UGG3C1 / CFO Datawarehouse Core Solutions Member of the Crossfunctions-Team UniCredit Global Information Services S.p.A. (UGIS S.p.A.) Zweigniederlassung Österreich Nordbergstrasse 13 A-1090 Vienna Room: TZB-6.18 Tel: +43 1 71730 50499 Mobile: - mailto:thomas.schloegl@wave-solutions.com <mailto:anton.wazin@wave-solutions.com>

2 1

[lxml-dev] inconsistency in the text nodes?
by Hervé Cauwelier Nov. 16, 2009

Nov. 16, 2009

Hi, I've set up the following excerpt to reproduce it: >>> from lxml import etree >>> s = etree._ElementStringResult("herve") >>> u = etree._ElementUnicodeResult(u"Hervé") >>> print s.getparent() Traceback (most recent call last): File "<input>", line 1, in <module> File "extensions.pxi", line 603, in lxml.etree._ElementStringResult.getparent (src/lxml/lxml.etree.c:99519) AttributeError: '_ElementStringResult' object has no attribute '_parent' >>> print u.getparent() None I'd like both of them to have the same behaviour, my personal preference being returning None. I guess it would look like that: --- lxml/extensions.pxi.orig 2009-11-13 09:46:27.760913564 +0100 +++ lxml/extensions.pxi 2009-11-13 09:46:34.869420791 +0100 @@ -597,6 +597,8 @@ return self._parent class _ElementStringResult(str): + cdef _Element _parent + cdef readonly object is_tail + cdef readonly object is_text + cdef readonly object is_attribute + # we need to use a Python class here, str cannot be C-subclassed # in Pyrex/Cython def getparent(self): I'm playing with these directly because I need to wrap them. Regards, Hervé

2 2