lxml - The Python XML Toolkit March 2015

lxml@python.org

13 participants
13 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

Etree to string problematic?
by Alex Boese 27 Mar '15

27 Mar '15

I noticed a strange behavior, and can only describe it as the code I write is fully owned my those who employ me. I was utilizing an lxml iterator routine to go through all of the nodes in some xml documents to look for differences. Now, because of the rigor of this computation, I had decided to convert some of these elements to string using the etree function by the same name. What I have observed in practice, but not expected, is that sometimes the tostring function will append a carriage return to the output. This seems to occur when there is white space between the closing tag and the next tag, which in this case was another closing tag. So if I had two duplicate documents which I nicened using "xmllint --format filename" and added a carriage return to the second which was just outside of the closing tag, something like this might occur. So everything between tags would be precisely the same, and then an extra carriage return after end tag would cause the tostring to output different. I'm using a version of Python 2. I could probably post version of lxml and libxml2 additionally. Has anyone had this experience? Sent from my Planet

2 1

XML parsing and CDATA
by Jens Tröger 26 Mar '15

26 Mar '15

Hi, The following is based on this question here: http://stackoverflow.com/questions/28398651/how-to-generate-markup-inside-o… What I ended up using in my XSLT stylesheet was something along these lines: <xsl:attribute name="bla"> <![CDATA[Here is <em>some</em>verbatim text with id="]]> <xsl:value-of select="@id"/> <![CDATA[" and <strong>more</strong> stuff.]]> </xsl:attribute> This worked reliably. However, this worked only after a seemingly subtle fix to the text itself! Initially I had something like id-<xsl:value-of select="@id"/> i.e. there was some text before that <xsl:value>. This worked sometimes, but not others where suddenly the CDATA following that text/element combination was swallowed away. Removing any text around the <xsl:value> seems to work in all cases though. Unfortunately, the document is too large to send and I don't really have the time to build a small test case which illustrates this problem. But it seems to me that there is a parser issue here when multiple CDATA inside of the <xsl:attribute> were combined with text and another element like <xsl:value>. There was no error message, just garbled output. Cheers, Jens -- Jens Tröger http://savage.light-speed.de/

2 6

how to make a unicode string valid for xml?
by Burak Arslan 21 Mar '15

21 Mar '15

Hello, I'm looking for a function like xml_unicode(some_unicode_string, 'ignore') that works like unicode(some_string, 'utf8', 'ignore'). Does lxml export such a function? I looked around the source but I didn't see any. Best regards, Burak

2 1

Inclusion of lxml-cffi into lxml
by Maciej Fijalkowski 18 Mar '15

18 Mar '15

Hi What it would take to include lxml-cffi (https://github.com/amauryfa/lxml/tree/cffi) as an official part of lxml? It works better on PyPy (with the original lxml being slow and prone to bugs, notably segfaulting for me) Cheers, fijal

2 3

Why the character apostrophe is not escaped?
by Omar Gutiérrez 11 Mar '15

11 Mar '15

I was wondering why the apostrophe is not automatically escaped as other characters? For example: < is transformed to *<* and > is transformed to *>* but ' is not transformed to *'* Python : sys.version_info(major=2, minor=7, micro=6, releaselevel='final', serial=0) lxml.etree : (3, 3, 3, 0) libxml used : (2, 9, 1) libxml compiled : (2, 9, 1) libxslt used : (1, 1, 28) libxslt compiled : (1, 1, 28)

3 4

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 March 2015