Mailman 3 November 2020 - lxml - The Python XML Toolkit

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

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

April 10, 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. 31, 2022

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

Accessing variables from within an XSL file
by Adrian Bool April 5, 2021

April 5, 2021

Hi, I'm trying to extract from data from XSL files on an IBM DataPower system. I can't change the XSLT files - and therefore need to work around their current structure to get the info I need. I'm doing this from within Python 3.7 using etree.__version__ 4.3.3. Here are my imports, a dummy XML object and a cutdown version of the XSL file from the IBM system: from lxml import etree from textwrap import dedent xml = etree.XML("""<root></root>""") xsl = etree.XML(dedent( """<?xml version="1.0"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:dp="http://www.datapower.com/extensions" extension-element-prefixes="dp"> <xsl:template match="node()|@*"> <xsl:copy> <xsl:apply-templates select="node()|@*"/> </xsl:copy> <xsl:variable name="destination_url"> <xsl:value-of select="'https://my.domain.example.com/'" /> </xsl:variable>  <dp:set-variable name="'var://context/mpgw/Destination'" value="$destination_url" /> </xsl:template> </xsl:stylesheet> """)) My goal is to use lxml to process this file and extract the contents of the DataPower variable 'var://context/mpgw/Destination' - i.e. the contents of the xsl:variable $destination_url - in the above case ' https://my.domain.example.com/'. I've created an XSLT extension for the "dp:set-variable" element to try to capture this information: class MyExtElement(etree.XSLTExtension): def execute(self, context, self_node, input_node, output_parent): if self_node.tag == '{ http://www.datapower.com/extensions}set-variable': print(f"Setting variable of name {self_node.get('name')} to value {self_node.get('value')}") extensions = { ('http://www.datapower.com/extensions', 'set-variable') : MyExtElement() } result = etree.XSLT(xsl, extensions=extensions)(xml) print(f"Result: {result}") When this is being called; instead of the value of destination_url I'm getting the static "$destination_url" string instead - with the output of the above script being: Setting variable of name 'var://context/mpgw/Destination' to value $destination_url Result: <?xml version="1.0"?> <root/> I am rather suprised that the $destination_url xsl:variable was not being evaluated - does anyone know why this is the case? Given the above, I've been trying to find a way to access the $destination_url xsl:variable from within my XSLTExtension - but unfortunately with no luck. Some things I've tried: * Calling self.process_children(context) within the extension - this just results in an empty list. * I've used dir() to look through the context, self_node and input_node args to try to find somewhere the variables may be accessible but with no luck. * I've used deepcopy to clone self_node to get an xpath function on this argument and made some attempts at using xpath to access the xsl variable - all unsuccessful: node = deepcopy(self_node) node.xpath("""<xsl:value-of select="$destination_url">""") *** lxml.etree.XPathEvalError: Invalid expression node.xpath("""$destination_url""") *** lxml.etree.XPathEvalError: Undefined variable node.xpath("""xsl:$destination_url""") *** lxml.etree.XPathEvalError: Invalid expression node.xpath("""xsl:$destination_url""", namespaces={'xsl':'http://www.w3.org/1999/XSL/Transform'}) *** lxml.etree.XPathEvalError: Invalid expressio node.xpath("""$destination_url""", namespaces={'xsl':'http://www.w3.org/1999/XSL/Transform'}) *** lxml.etree.XPathEvalError: Undefined variable node.xpath("""/xsl:$destination_url""", namespaces={'xsl':'http://www.w3.org/1999/XSL/Transform'}) *** lxml.etree.XPathEvalError: Invalid expression node.xpath("""<xsl:value-of select="$destination_url">""", namespaces={'xsl':'http://www.w3.org/1999/XSL/Transform'}) *** lxml.etree.XPathEvalError: Invalid expression I'm lost now! Any suggestions greatly appreciated! Cheers, aid

4 5

Re: [lxml] Test whether a (removed?) element is in an element tree
by Holger.Joukl＠LBBW.de Nov. 14, 2020

Nov. 14, 2020

Hi, > Suppose I have an element tree: > > xml = lxml.etree.XML(b"<a>bla <b>bla</b> bla <c>bla</c> bla <d/> bla</a>”) > > and I get all of its elements: > > elems = xml.xpath(".//*”) > [<Element b at 0x10d1dad70>, <Element c at 0x10d1dad20>, <Element d at > 0x10d1dacd0>] > > Next, I remove some element from that tree: > > c = xml.find("c”) # = elems[1] > c.getparent().remove(c) > > How can I now test whether that element is still in the element tree? > > c.getparent() # elems[1].getparent() > > returns None, but is that a sure test? I can’t find documentation on how to identify > elements that don’t belong to a given element tree. IIRC: getparent() also returns None for a root element. As far as I remember each element always belongs to one unique tree, which gets created on-the-fly for an element that you remove from a tree. So I don't quite see the usecase, but you could check if c.getroottree() is the same tree object as your original/other tree (i.e. xml.getroottree()). 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.

2 1

Re: [lxml] XRD validation
by Holger.Joukl＠LBBW.de Nov. 14, 2020

Nov. 14, 2020

I'm using lxml to verify an XML against an XRD schema, but I'm using some of the features of v1.1 which gave me an error during validation with lxml: […] Line 107 is the part where a new feature is being used (test="...") Is this a normal behavior of lxml? Are there plans to support v1.1 https://www.w3.org/TR/xmlschema11-1/#intro1.1 See https://mailman-mail5.webfaction.com/pipermail/lxml/20170104/023650.html (last time I looked, i.e. I didn’t check for new developments). Best regards, Holger [cid:image001_e3261df1-efb3-4c64-a4de-9b63c5e52cfb.png]<https://www.lbbw.de/> [cid:image002_15f56f09-b8fe-4ddc-a247-e3cf3d25c71f.png]<https://twitter.com/lbbw> [cid:image003_e01dca75-944e-4ea3-8463-c9c061e5b36b.png] <https://www.linkedin.com/company/lbbw> [cid:image004_5642e2b4-e190-4f0c-a274-7ceb59fe913c.png] <https://www.xing.com/company/lbbw> [cid:image005_53d53024-7202-4d60-8d95-dc0f361239ca.png] <https://www.facebook.com/LBBW.Stuttgart/> [cid:image006_9c0b6462-8935-4b9c-9fe3-0caa90d8623b.png] <https://www.youtube.com/user/LBBWDirekt> [cid:image007_9a7ebd18-8e4e-4c3e-931a-ecc4bf575ace.png] <https://www.instagram.com/lbbw_karriere/> 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

Test whether a (removed?) element is in an element tree
by Jens Tröger Nov. 11, 2020

Nov. 11, 2020

Hello, Suppose I have an element tree: xml = lxml.etree.XML(b"<a>bla <b>bla</b> bla <c>bla</c> bla <d/> bla</a>”) and I get all of its elements: elems = xml.xpath(".//*”) [<Element b at 0x10d1dad70>, <Element c at 0x10d1dad20>, <Element d at 0x10d1dacd0>] Next, I remove some element from that tree: c = xml.find("c”) # = elems[1] c.getparent().remove(c) How can I now test whether that element is still in the element tree? c.getparent() # elems[1].getparent() returns None, but is that a sure test? I can’t find documentation on how to identify elements that don’t belong to a given element tree. Much thanks! Jens -- Jens Tröger http://savage.light-speed.de/

1 0

XRD validation
by jeroen-boonen＠telenet.be Nov. 10, 2020

Nov. 10, 2020

Hi, I'm using lxml to verify an XML against an XRD schema, but I'm using some of the features of v1.1 which gave me an error during validation with lxml: xrd snipped: <xs:element minOccurs ="0" maxOccurs="unbounded" name="parameter"> <xs:alternative type="parameterTypeVoid" test="@type = 'void'"/> <xs:alternative type="parameterTypeVarArgs" test="@type = ''"/> <xs:alternative type="parameterTypeNormal" /> <xs:unique name="UniqueAliasName"> <xs:selector xpath="alias" /> <xs:field xpath="@name" /> </xs:unique> </xs:element> error generated by lxml: xmlschema = etree.XMLSchema(xmlschema_doc) File "src\lxml\xmlschema.pxi", line 88, in lxml.etree.XMLSchema.__init__ lxml.etree.XMLSchemaParseError: Element '{http://www.w3.org/2001/XMLSchema}element': The content is not valid. Expected is (annotation?, ((simpleType | complexType)?, (unique | key | keyref)*))., line 107 Line 107 is the part where a new feature is being used (test="...") Is this a normal behavior of lxml? Are there plans to support v1.1 [ https://www.w3.org/TR/xmlschema11-1/#intro1.1 | https://www.w3.org/TR/xmlschema11-1/#intro1.1 ] BR, Jeroen

1 0