Mailman 3 July 2022 - lxml - The Python XML Toolkit

[lxml-dev] lxml has its page on launchpad
by Stefan Behnel 10 Apr '23

10 Apr '23

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 09 Apr '23

09 Apr '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/>

6 6

[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] 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

Question about inheritance in cssselect.py
by Dani Litovsky Alcala 23 Dec '22

23 Dec '22

lxml v.4.9 cssselect.py:CSSSelector.__init__ calls on `etree.XPath.__init__(self, path, namespaces=namespaces)` to initialize the parent class. Is there a reason why `super()` or even `super(CSSSelector, self)__init__...` is not used? I bring this up as if I attempt to monkey patch (private project) `etree.XPath.__init__` the current code causes an error ``` TypeError: super(type, obj): obj must be an instance or subtype of type ``` while replacing it with the suggested use of `super()` fixes my error.

3 3

can I tell lxml to ignore xmlids?
by Martin Mueller 31 Oct '22

31 Oct '22

Duplicate xmlids have way of creeping into my 60,000 documents. The ids keep the document from parsing, which is helpful in drawing attention to errors, but it makes it harder to correct the errors. I work with documents in the TEI namespace, and I have a very kludgy workaround: I comment out the reference to the schema and change ‘xml:id ‘ to ‘xmlom’. Then I can loop through the document and fix errors with a script. There must be a more elegant way to do this. Is there away of telling lxml: “never mind the duplicate IDs. Just carry on”. Then I can toggle between a script that cares or doesn’t care about duplicate IDS. With thanks in advance for any help Martin Mueller Professor emeritus of English and Classics Northwestern University

4 4

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

30 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: Why does it fail cleaning GPX file?
by Holger.Joukl＠LBBW.de 22 Jul '22

22 Jul '22

Hi, > I run this script to remove unneeded elements. > > For some reason, the input file is left as-is, when I try to get rid of the <metadata> > block; If works as expected when I ignore that element. > > Any idea why? The reason is that lxml (sensibly) uses fully qualified tag names in Clark notation (see http://www.jclark.com/xml/xmlns.htm) > > ========== INPUT.GPX > > <?xml version="1.0" encoding="UTF-8"?> > <gpx version="1.1" creator="GPSBabel - http://www.acme.com" > xmlns="http://www.topografix.com/GPX/1/1" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> > <metadata> > <time>2022-07-21T20:29:48.309Z</time> > <bounds minlat="44.456597300" minlon="3.007453400" > maxlat="45.803699000" maxlon="5.251047400"/> > </metadata> > <wpt lat="45.042569200" lon="5.040802200"> > <name>way/4749044</name> > <cmt>landuse=cemetery</cmt> > <desc>landuse=cemetery</desc> > <link href="http://osm.org/browse/way/4749044"/> > </wpt> > </gpx> Here, your actual xml elements are e.g. "{http://www.topografix.com/GPX/1/1}cmt" (in Clark notation), not plain "cmt", since all elements without a namespace prefix due to this namespace declaration xmlns="http://www.topografix.com/GPX/1/1" belong to said namespace. So you must iter() over the proper fully-qualified names. Here's a slightly adapted version of your example code that hopefully shows what's going on and how to do that: # modified element cleaning sample xmldata = """<?xml version="1.0"?> <gpx version="1.1" creator="GPSBabel - http://www.acme.com" xmlns="http://www.topografix.com/GPX/1/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <metadata> ┆<time>2022-07-21T20:29:48.309Z</time> ┆<bounds minlat="44.456597300" minlon="3.007453400" maxlat="45.803699000" maxlon="5.251047400"/> </metadata> <wpt lat="45.042569200" lon="5.040802200"> ┆<name>way/4749044</name> ┆<cmt>landuse=cemetery</cmt> ┆<desc>landuse=cemetery</desc> ┆<link href="http://osm.org/browse/way/4749044"/> </wpt> </gpx> """ import lxml.etree as et parser = et.XMLParser(remove_blank_text=True, strip_cdata=False) root = et.fromstring(xmldata, parser) # Show the fully qualified tag names (Clark-Notation) for el in root.iter(): print(el.tag) # Remove by fully-qualified Clark tag name or using a wildcard, if appropriate # (unqualified link will not get removed here since this doesn't exist - left in for # demo purposes) for el in root.iter('{http://www.topografix.com/GPX/1/1}cmt','{*}desc','link'): ┆parent = el.getparent() ┆parent.remove(el) print(et.tostring(root, pretty_print=True, encoding='unicode')) (I skipped the file reading/writing for my convenience; you might also want to look at the pathlib standard library module for you file/path name constructions, which is nice for handling such stuff, sometimes) HTH, 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.

2 1

Why does it fail cleaning GPX file?
by Gilles 21 Jul '22

21 Jul '22

Hello, I run this script to remove unneeded elements. For some reason, the input file is left as-is, when I try to get rid of the <metadata> block; If works as expected when I ignore that element. Any idea why? Thank you. ========== INPUT.GPX <?xml version="1.0" encoding="UTF-8"?> <gpx version="1.1" creator="GPSBabel - http://www.acme.com" xmlns="http://www.topografix.com/GPX/1/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <metadata> <time>2022-07-21T20:29:48.309Z</time> <bounds minlat="44.456597300" minlon="3.007453400" maxlat="45.803699000" maxlon="5.251047400"/> </metadata> <wpt lat="45.042569200" lon="5.040802200"> <name>way/4749044</name> <cmt>landuse=cemetery</cmt> <desc>landuse=cemetery</desc> <link href="http://osm.org/browse/way/4749044"/> </wpt> </gpx> ========== CLEAN.PY import lxml.etree as et from lxml import html #from xml.etree.ElementTree import XML, fromstring #import re import sys import os item= "input.gpx" BASENAME, EXTENSION = os.path.splitext(os.path.basename(item)) OUTPUTFILE = f"{BASENAME}.EDITED{EXTENSION}" PATH=os.path.dirname(os.path.abspath(item)) OUTPUT_FULLPATH=f"{PATH}\{OUTPUTFILE}" parser = et.XMLParser(remove_blank_text=True,strip_cdata=False) tree = et.parse(item,parser) root = tree.getroot() #=========== Remove blocks/elements #BAD for el in root.iter('cmt','desc','link','metadata'): #BAD for el in root.iter('metadata','cmt','desc','link'): #OK for el in root.iter('cmt','desc','link'): parent = el.getparent() parent.remove(el) #Write modified tree to new file tree.write(OUTPUT_FULLPATH, xml_declaration=True,pretty_print=True,encoding='UTF-8')

1 0

Tested value modified in validation error message
by Bob Kline 15 Jul '22

15 Jul '22

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