Mailman 3 January 2022 - lxml - The Python XML Toolkit

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

11 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 10 Apr '23

10 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

[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

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

16 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

Support for XSL/T 2.0
by Bob Kline 17 Feb '22

17 Feb '22

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

Restricting third party access for lxml github org?
by Martijn Faassen 25 Jan '22

25 Jan '22

Hey lxmlers, I recently found out that older organizations by default grant third party access to any github OAuth application that a user has enabled. This means that if any of such applications is compromised, this organization is open for attack. I therefore would recommend we go amend that here: https://github.com/organizations/lxml/settings/oauth_application_policy <https://github.com/organizations/fanstatic/settings/oauth_application_policy> I don't think it has huge consequences as you can selectively enable those applications you trust after that, but I figured people using this org should be aware before it's enabled. Regards, Martijn

2 1

Re: source location or ordering of tag
by Holger.Joukl＠LBBW.de 21 Jan '22

21 Jan '22

Hi Robin, > I am trying to port an xml parser to using lxml.etree. > > I can get the parser to work find and get it to validate properly and produce a > parse tree in tuple form ie (tag, attrib, [contents...], extra) > > The standard xml error locations are find and provide both line number and > column. > > However, the current parser allows for debugging during post processing of the > parse and it has a tuple of information in place of extra above that looks like > ((srcname,startline,startcolumn),(srcname,endline,endcolumn)). This extra > information allows post analysis to determine if one tag starts after another. > > I can find no way to access the column information in the standard parsers. > > I believe that the information is present in the XMLReader that libxml2 provides, > but no way to get access in lxml. I believe that you're right. > I think I just need to determine a tag ordering ie does tag0 start before or after > tag1 in the source. > > Is there an obvious way to do that? > > Currently (tag0.startline, tag0.startcolumn) is compared with (tag1.startline, > tag1.startcolumn) and the latest tag is returned. > > I believe I could just add a tag sequence to determine order, but is there an easier > way? I must say I don't quite understand the problem: You're probably using event-driven parsing (https://lxml.de/tutorial.html#parsing-from-strings-and-files) to feed into your parser (on top of lxml's parsing)? Why would you have the need to compare tag lines and columns, since elements (and respective parsing events) are guaranteed to come in order? Are you concerned with the innermost (opening) tag on a certain line, or what are you looking for? 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

source location or ordering of tag
by Robin Becker 20 Jan '22

20 Jan '22

I am trying to port an xml parser to using lxml.etree. I can get the parser to work find and get it to validate properly and produce a parse tree in tuple form ie (tag, attrib, [contents...], extra) The standard xml error locations are find and provide both line number and column. However, the current parser allows for debugging during post processing of the parse and it has a tuple of information in place of extra above that looks like ((srcname,startline,startcolumn),(srcname,endline,endcolumn)). This extra information allows post analysis to determine if one tag starts after another. I can find no way to access the column information in the standard parsers. I believe that the information is present in the XMLReader that libxml2 provides, but no way to get access in lxml. I think I just need to determine a tag ordering ie does tag0 start before or after tag1 in the source. Is there an obvious way to do that? Currently (tag0.startline, tag0.startcolumn) is compared with (tag1.startline, tag1.startcolumn) and the latest tag is returned. I believe I could just add a tag sequence to determine order, but is there an easier way? -- Robin Becker

1 0