lxml - The Python XML Toolkit July 2009

lxml@python.org

29 participants
37 discussions

[lxml-dev] Reparenting a node
by Lawrence Oluyede 30 Jan '23

30 Jan '23

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] Checking whether a node is a comment/element
by Geoffrey Sneddon 11 Jan '23

11 Jan '23

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/>

4 4

[lxml-dev] lxml 2.0.5 released
by Stefan Behnel 11 Jan '23

11 Jan '23

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] lxml has its page on launchpad
by Stefan Behnel 21 Sep '22

21 Sep '22

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

3 2

[lxml-dev] Building LXML Trunk
by Sidnei da Silva 31 Aug '22

31 Aug '22

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

Re: [lxml-dev] About the position of html parsing by HTML Target parser
by Stefan Behnel 09 Aug '09

09 Aug '09

[bringing this back to the list] Nicholas Dudfield wrote: >>> even then it's only a *byte* at a time, not a *character* at a time). > > I have been feeding it a unicode character at a time and tested it > with some Chinese characters. Ah, sure, that works. >> Searching for the >> above regexp is safe as "<" cannot occur anywhere in the XML data stream >> except for a tag start/end or comment/PI > > or in embedded <script></script> with CDATA eg > $("someSelector").html('<p> ...') Right, I keep forgetting that CDATA is evil. But you can check for CDATA as well. > For clarification, you are saying skip the target parser and feeding > process and just iterate over the elements and regex for the tags? > something like "<tagname\s" but accounting for tags such as <br/> etc I'd try that, yes. Should be a lot faster as you only handle the elements in your code, not the text content, for example. And you always know exactly what the next opening/closing tag must be. You can special case self-closing tags by checking for contained text and children. If there isn't anything in them, be prepared to find the next opening element before finding a closing tag. Having the parsed tree available gives you a lot of information that you can exploit. You may also consider using something like ahocorasick to search for all opening tags at once (note that lxml makes the namespace prefix available for each Element), plus "<![CDATA". Then double-check the result by traversing the tree and fixing up any false positives 'somehow'. http://hkn.eecs.berkeley.edu/~dyoo/python/ahocorasick/ >> I will also check if there is a way to provide the position at the (target) >> parser level, but that needs to fit the current interface. And I currently >> do not have much time to dig into this. > > That would be awesomely ideal :) ... although not that helpful, as I just noted in another post. So I don't think this is a viable solution for now. Stefan

2 11

[lxml-dev] Bug with whitespace in namespaces
by Christian Zagrodnick 08 Aug '09

08 Aug '09

Hoi, it is possible to create invalid XML with lxml: >>> import lxml.etree >>> import lxml.objectify >>> xml = lxml.objectify.XML('<a/>') >>> xml.set('{a b}c', 'foo') # This should fail! >>> lxml.etree.tostring(xml) '<a xmlns:ns0="a b" ns0:c="foo"/>' >>> lxml.objectify.fromstring(lxml.etree.tostring(xml)) Traceback (most recent call last): ... File "parser.pxi", line 625, in lxml.etree._handleParseResult (src/lxml/lxml.etree.c:64741) File "parser.pxi", line 565, in lxml.etree._raiseParseError (src/lxml/lxml.etree.c:64084) lxml.etree.XMLSyntaxError: xmlns:ns0: 'a b' is not a valid URI, line 1, column 13 >>> Regards, -- Christian Zagrodnick · cz(a)gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 4 · fax +49 345 1229889 1 Zope and Plone consulting and development

2 2

[lxml-dev] automatic attribute unicode decode?
by Hervé Cauwelier 06 Aug '09

06 Aug '09

Hi, I'm quite puzzled by the following excerpt: >>> from lxml import etree >>> r = etree.fromstring('<root toto="français" titi="ascii" tata="1"/>' >>> r.attrib {'titi': 'ascii', 'toto': u'fran\xe7ais', 'tata': '1'} In a bare document with no encoding declaration, lxml has decoded itself a string that did not match the ascii table (what heuristic did it use?). Now I have three attributes of two different types. I wonder why the integer was not decoded. ;-) I actually found this in a real-world document with encoding and namespaces (An ODF xml part). Is this a bug to report and how to circumvent it? Thanks, Hervé

3 2

[lxml-dev] Whitespace foiling pretty_print - any fix?
by B Wooster 06 Aug '09

06 Aug '09

f an XML element has whitespace along with sub elements, pretty_print does not work well. This is probably a XML whitespace issue, but is there any way to work around this issue? Here's example code and the output it prints, and what I would like to get: from lxml import etree as ET root = ET.XML("""<a> <b>test</b> </a>""") ET.SubElement(root, "c") ET.SubElement(root, "d") print ET.tostring(root, pretty_print=True) # This prints: """<a> <b>test</b> <c/><d/></a> """ # Would like: """<a> <b>test</b> <c/> <d/> </a> """

2 1

[lxml-dev] Strange segmentation fault if class inherited from objectify.ObjectifiedElement
by Daniel Albeseder 06 Aug '09

06 Aug '09

I just tried this and got an segmentation fault :-( Python 2.6.2 (release26-maint, Apr 19 2009, 01:58:18) [GCC 4.3.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from lxml import objectify >>> from lxml import etree >>> >>> print etree.LXML_VERSION, etree.LIBXML_VERSION (2, 2, 2, 0) (2, 6, 32) >>> >>> class test (objectify.ObjectifiedElement) : ... pass ... >>> good = objectify.Element ("abc") >>> print type (good), repr (good) <type 'lxml.objectify.ObjectifiedElement'> <Element abc at 7f0797587fc8> >>> >>> bad = test ("abc") Segmentation fault I read that you have to instantiate a parser with objectify.makeparser and use the method makeelement from there. However I would expect that at least not Segmentation Fault happens, if someone is using the normal inheritance as used to be. regards Daniel

2 1

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

lxml - The Python XML Toolkit July 2009