Mailman 3 February 2022 - lxml - The Python XML Toolkit

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

April 10, 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 9, 2023

April 9, 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. 30, 2022

Aug. 30, 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

Tested value modified in validation error message
by Bob Kline July 15, 2022

July 15, 2022

Before I file a ticket, I wanted to check here to find out if this is a known problem (I searched the bug tracker, but didn't see any matches). Our customer is using a commercial XML editor and the editor's implementation of the DOM API sometimes garbles whitespace inside text nodes when serializing XML documents for the document's xml property. This causes schema validation errors when we send that serialization off to be validated against the document type's schema using lxml. The problem we have run into with lxml is that the message property of the error object which comes back in the schema object's error_log has altered the value being validated. So, for example, if the text content of an element in the serialized DOM is "Processing\ncomplete" and the value it was supposed to match in the enumerated valid values is "Processing complete" then the message attribute for the corresponding object in the error_log has Element 'ProcessingStatusValue': [facet 'enumeration'] The value 'Processing complete' is not an element of the set {'Ready for English peer review', 'Ready for English scientific review', 'Ready for English OCCM review', 'Ready for Spanish peer review', 'Ready for Spanish OCCM review', 'Ready for publishing', 'Ready for translation', 'Processing complete'}. In effect saying "the value 'Processing complete' does not match the value 'Processing complete'." Took a very long time for us to figure out that the error message was wrong, and that it should have said ... The value 'Processing\ncomplete' is not an element of the set .... -- Bob Kline https://www.rksystems.com mailto:bkline@rksystems.com

4 10

Re: python lxml.objectify gives no attribute access to gco:CharacterString node
by Holger.Joukl＠LBBW.de March 3, 2022

March 3, 2022

Hi Volker, > A week ago I formulated a quite simple lxml.objectify question on stackoverflow and got no answer, yet. > https://stackoverflow.com/questions/71212909/python-lxml-objectify-gives-no… > Since I don't get an easy answer I conclude that my feeling about something is wrong in lxml.objectfy is not a mare. > So I elevate this topic to the mailing list. > Any help appreciated > Volker Jaenisch This is expected and just how lxml.objectify works. Since {http://www.isotc211.org/2005/gco}CharacterString is from another namespace than its parent element ({"http://www.isotc211.org/2005/gmd}fileIdentifier) it cannot be retrieved from the parent with "simple (dot) attribute lookup". Instead you have to you use index access (just like you already did) or getattr: ``` >>> from lxml import etree, objectify >>> data = objectify.fromstring( ... """<gmd:MD_Metadata ... xmlns:gmd="http://www.isotc211.org/2005/gmd" ... xmlns:gco="http://www.isotc211.org/2005/gco" > ... <gmd:fileIdentifier> ... <gco:CharacterString>2ce585df-df23-45f6-b8e1-184e64e7e3b5</gco:CharacterString> ... </gmd:fileIdentifier> ... <gmd:language> ... <gmd:LanguageCode codeList="https://www.loc.gov/standards/iso639-2/" codeListValue="ger">ger</gmd:LanguageCode> ... </gmd:language> ... </gmd:MD_Metadata> ... """) >>> data.fileIdentifier["{http://www.isotc211.org/2005/gco}CharacterString"] '2ce585df-df23-45f6-b8e1-184e64e7e3b5' >>> getattr(data.fileIdentifier, "{http://www.isotc211.org/2005/gco}CharacterString") '2ce585df-df23-45f6-b8e1-184e64e7e3b5' >>> ``` The reason for this is that obviously {http://www.isotc211.org/2005/gco}CharacterString is not a valid Python identifier and it makes sense to restrict unqualified lookup to children from the same namespace. See also "Namespace handling" in the official docs: https://lxml.de/objectify.html#the-lxml-objectify-api Best, Holger Landesbank Baden-Wuerttemberg Anstalt des oeffentlichen Rechts Hauptsitze: Stuttgart, Karlsruhe, Mannheim, Mainz HRA 12704 Amtsgericht Stuttgart HRA 4356, HRA 104 440 Amtsgericht Mannheim HRA 40687 Amtsgericht Mainz Die LBBW verarbeitet gemaess Erfordernissen der DSGVO Ihre personenbezogenen Daten. Informationen finden Sie unter https://www.lbbw.de/datenschutz.

4 5

python lxml.objectify gives no attribute access to gco:CharacterString node
by Dr. Volker Jaenisch Feb. 27, 2022

Feb. 27, 2022

Dear xlml specialists! A week ago I formulated a quite simple lxml.objectify question on stackoverflow and got no answer, yet. https://stackoverflow.com/questions/71212909/python-lxml-objectify-gives-no… <https://stackoverflow.com/questions/71212909/python-lxml-objectify-gives-no…> Since I don't get an easy answer I conclude that my feeling about something is wrong in lxml.objectfy is not a mare. So I elevate this topic to the mailing list. Any help appreciated Volker Jaenisch -- ========================================================= inqbus Scientific Computing Dr. Volker Jaenisch Hungerbichlweg 3 +49 (8860) 9222 7 92 86977 Burggenhttps://inqbus.de =========================================================

1 0

v4.8.0 breaking regression?
by Jens Tröger Feb. 23, 2022

Feb. 23, 2022

Hello, After updating to v4.8.0 this morning, entire workflows started to fail. After some digging around I could narrow it down to a regression introduced between v4.7.1 and v4.8.0. This example code import lxml.etree xml = lxml.etree.XML(""" <a> <c id="b-1-c">baz</c> <c id="b-2-c">baz</c> <c id="b-3-c">baz</c> </a> """) print(len(xml)) for elm in xml: print(elm, lxml.etree.tostring(elm)) On v4.7.1 I get the expected result 3 <Element b at 0x10ad5d080> b'\n <c id="b-1-c">baz</c>\n \n ' <Element b at 0x10ad5d100> b'\n <c id="b-2-c">baz</c>\n \n ' <Element b at 0x10ad5d140> b'\n <c id="b-3-c">baz</c>\n \n’ On v4.8.0 the following: 3 <Element b at 0x1061cc100> b'\n <c id="b-1-c">baz</c>\n \n \n <c id="b-2-c">baz</c>\n \n \n <c id="b-3-c">baz</c>\n \n</a>\n ' <Element b at 0x1061cc180> b'\n <c id="b-2-c">baz</c>\n \n \n <c id="b-3-c">baz</c>\n \n</a>\n ' <Element b at 0x1061cc1c0> b'\n <c id="b-3-c">baz</c>\n \n</a>\n’ Now scale that for nodes with hundreds of children and you’ll get an idea of what happened this morning 😉 Cheers, Jens -- Jens Tröger https://savage.light-speed.de/

4 22

Support for XSL/T 2.0
by Bob Kline Feb. 17, 2022

Feb. 17, 2022

Will lxml ever support XSL/T 2.0 (which achieved recommendation status 15 years ago)? Thanks. -- Bob Kline https://www.rksystems.com mailto:bkline@rksystems.com

2 3