Mailman 3 June 2023 - lxml - The Python XML Toolkit

lxml children vs. descendant not working correctly (I think)
by wayneb＠mac.com July 2, 2023

July 2, 2023

Here's a bit of code I was trying to parse: <div data-flag="TODO"> <p>This content is flagged as <code>TODO</code>. It gets a background colour (red, in this case) and the label <code>TODO</code> is rendered into the document margin.</p> </div> I was using .//div/child::* What I got back was a list of three items: <p><code><code> those aren't the children of div! Those are the descendant elements of div. I decided to test this using .//div/descendant::* which gave me the proper: <p><code><code> elements. To further confirm this I used other parsers and they provided the proper child (p in this case). How do we go about getting this fixed in lxml?

2 1

Python 12 support is urgently needed!
by Arcadiy Ivanov June 30, 2023

June 30, 2023

Hello, lxml fails to compile on Python 12 and there are no binary distributions available of it from PyPI either. Please see the bug https://bugs.launchpad.net/lxml/+bug/2024719 lxml underlies a lot of libraries and absence of Python 12 support makes it impossible to test the recent betas of those products. Regards, -- Arcadiy Ivanov arcadiy(a)ivanov.biz | @arcivanov | https://ivanov.biz https://github.com/arcivanov

2 3

Re: a simple question about a tricky problem
by Holger.Joukl＠LBBW.de June 16, 2023

June 16, 2023

Hi Martin, did you solve your problem by now? > I use lxml to work with a large collection of TEI-encoded texts(66,000) that are linguistically annotated. Each token is wrapped in a <w> or <pc> element with a unique ID and various attributes. > I can march through the texts at the lowest level of <w> and <pc> elements without paying any attention to the discursive structure of higher elements. I just do > > for w in tree.iter(tei + ‘w’, tei + ‘pc’: > if x: > do this > if y: > do that > > But now I want to create a concordance in which tokens meeting some condition are pulled out and surrounded with seven words on either side. I do this with itersiblings(), but that is a tricky operation. > The next <w> token may not be a sibling but a child of a higher level sibling. Remembering that “elements are lists” you have patterns like > > [a, b, c, [d, e, f] g, h, i, [k, l, m, n] > Would that be s.th. like the found <w> word element sits in a relative clause which is a nested clause in a sentence/main clause, and you'd like to find surrounding words crossing the relative clause's end, i.e. also from the higher level? Sorry if I'm not using proper terminology here - not a native English speaker, my grammar knowledge is rusty and I'm not familiar with the TEI structure. Could you maybe give a very small + simple ("minimal") example of such a TEI-encoded text that illustrates the problem? Should be a working TEI-XML file, i.e. parsable with lxml. > Getting from ‘c’ to ‘d’ is one thing, getting from ‘f’ to ‘g’ is another. In a large archive of sometimes quite weird encodings, the details become very hairy very fast. Is there are some “Gordian knot” solution, > or does one just figure out this obstacle race one detail at a time? There are “soft” tags that do not break the continuity of a sentence (hi), hard tags that mark an end beyond which you don’t want to go > anyhow (p), and “jump tags” (note) where your “next sibling” is the first <w> after the <note> element, which may be quite long. Are there some higher level structures which boundaries' your search for the surrounding 7 words should never cross? Then maybe you could instead iterate over these higher level structures, "flatten" all its <w> and <pc> (or any other relevant) descendants, ignoring <note>s, for further processing and then work on such a flattened list. Best regards, 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.

1 0

a simple question about a tricky problem
by Martin Mueller June 8, 2023

June 8, 2023

I use lxml to work with a large collection of TEI-encoded texts(66,000) that are linguistically annotated. Each token is wrapped in a <w> or <pc> element with a unique ID and various attributes. I can march through the texts at the lowest level of <w> and <pc> elements without paying any attention to the discursive structure of higher elements. I just do for w in tree.iter(tei + ‘w’, tei + ‘pc’: if x: do this if y: do that But now I want to create a concordance in which tokens meeting some condition are pulled out and surrounded with seven words on either side. I do this with itersiblings(), but that is a tricky operation. The next <w> token may not be a sibling but a child of a higher level sibling. Remembering that “elements are lists” you have patterns like [a, b, c, [d, e, f] g, h, i, [k, l, m, n] Getting from ‘c’ to ‘d’ is one thing, getting from ‘f’ to ‘g’ is another. In a large archive of sometimes quite weird encodings, the details become very hairy very fast. Is there are some “Gordian knot” solution, or does one just figure out this obstacle race one detail at a time? There are “soft” tags that do not break the continuity of a sentence (hi), hard tags that mark an end beyond which you don’t want to go anyhow (p), and “jump tags” (note) where your “next sibling” is the first <w> after the <note> element, which may be quite long. I am old enough to have grown up with Winnie the Poh and feel like “Bear of Very Little Brain” when confronted with these problems. I’ll be grateful for any advice, including a confirmation that it’s the just way it is. Martin Mueller Professor of English and Classics emeritus

4 3

Passing params to a schematron ?
by jrjsmrtn＠gmail.com June 7, 2023

June 7, 2023

According to the documentation (https://lxml.de/validation.html#id2), it is possible to pass parameters to a Schematron schema: | To set parameters for steps 1), 2) and 3) dictionaries containing parameters for XSLT can be provided using the keyword arguments include_params, | expand_params or compile_params. Schematron automatically converts these parameters to stylesheet parameters so you need not worry to set | string parameters using quotes or to use XSLT.strparam(). If you ever need to pass an XPath as argument to the XSLT stylesheet you can pass in an | etree.XPath object (see XPath and XSLT with lxml: Stylesheet-parameters for background on this). | | The phase parameter of the compile step is additionally exposed as a keyword argument. If set, it overrides occurrence in compile_params. Note that | isoschematron.Schematron might expose more common parameters as additional keyword args in the future. However, I cannot find a single example anywhere of how to access those parameters *in* the Schematron schema and have tried a lot of methods with no success... :-/ (And yes, I read https://github.com/Schematron/schema/blob/main/schematron.rnc & Co) Can anyone point me to a concrete example ? :-/ G.

1 0