Mailman 3 September 2016 - 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

htmlfile doesn't escape attribute values
by Burak Arslan Dec. 27, 2016

Dec. 27, 2016

Hello, This is a heads-up for bug 1594155 here: https://bugs.launchpad.net/lxml/+bug/1594155 Please consider the following test case. >>> from lxml import html >>> from lxml.etree import htmlfile >>> from lxml.html.builder import E >>> from StringIO import StringIO >>> out = StringIO() >>> with htmlfile(out) as f: ... with f.element("tagname", attrib={"attr": '"misquoted"'}): ... f.write("foo") ... >>> out.getvalue() '<tagname attr=""misquoted"">foo</tagname>' Expected output: '<tagname attr=""misquoted"">foo</tagname>' Lack of proper escaping confuses the hell out of browsers :) Proper escaping is needed to safely put html documents inside srcdoc attribute of an <iframe>. The workaround is to quote the data before putting it inside an attribute. Fortunately, only replacing " with " is enough and & is also not escaped (but it should be). versions: Python : sys.version_info(major=2, minor=7, micro=11, releaselevel='final', serial=0) lxml.etree : (3, 6, 0, 0) libxml used : (2, 9, 3) libxml compiled : (2, 9, 3) libxslt used : (1, 1, 28) libxslt compiled : (1, 1, 28) Best regards, Burak

1 1

XML schema validation error using 3.6.3
by Tom Kralidis Nov. 4, 2016

Nov. 4, 2016

Hi all: moving from 3.6.2 to 3.6.3 introduces an XML Schema validation error. Test case: XML document: https://github.com/geopython/pycsw/blob/master/tests/suites/default/post/Ge… Associated XML Schema: http://schemas.opengis.net/csw/2.0.2/CSW-discovery.xsd (note there are numerous includes/imports. Full schema tree can be downloaded from http://schemas.opengis.net/SCHEMAS_OPENGIS_NET.zip). Code snippet: schema = etree.XMLSchema(file='/path/to/csw/2.0.2/CSW-discovery.xsd') parser = etree.XMLParser(schema=schema, resolve_entities=False) doc = etree.fromstring(postdata, parser) Result: Element '{http://www.opengis.net/cat/csw/2.0.2}GetRecordById', attribute 'service': The value '(null)' does not match the fixed value constraint 'CSW'. Testing results summary [1]: - lxml 3.6.1 && libxml2 2.9.1 passes - lxml 3.6.2 && libxml2 2.9.1 passes - lxml 3.6.3 && libxml2 2.9.4 FAILS with said validation error - lxml 3.6.4 && libxml2 2.9.4 FAILS with said validation error Any ideas? Is this a libxml2 issue? I notice 3.6.2 uses libxml2 2.9.1 whereas 3.6.3 uses libxml2 2.9.4 (on travis, fwiw). Let me know if you need more info or a clearer test case, or if/where I should file an issue. Thanks ..Tom [1] https://github.com/geopython/pycsw/pull/453

2 2

transform using XSLT with method="text" has empty result
by Rainer Hoerbe Oct. 1, 2016

Oct. 1, 2016

I have a style sheet that outputs validation messages as JSON, i.e. output method=„text“. Using xsltproc from libxml2 yields a correct result: xsltproc rules/schtron_xsl/rule00I.xsl testdata/idp_valid.xml "00": { "Severity": "Info", "Message": "Validating entityID https://idp5.test.example.org/idp.xml", "Context“, "/md:EntitiesDescriptor[1]/md:EntityDescriptor[1]", "Rule": "@entityID" } Whereas I get an empty result with lxml: [https://github.com/identinetics/saml_schematron/blob/dev/scripts/try_xslt2t…] import lxml.etree as etree with open('rules/schtron_xsl/rule00I.xsl') as fd: transform = etree.XSLT(etree.XML(''.join(fd.readlines()))) with open('testdata/idp_valid.xml') as fd: md_dom = etree.parse(fd) result_xml = (transform(md_dom)) print(etree.tostring(result_xml)) (Data files relative to https://github.com/identinetics/saml_schematron/blob/dev/) What is the correct method to get non-XML result objects from xslt? Best regards Rainer Hörbe

3 6

Discrepancies between pickled objectified object and source objectified object ?
by Thibault Clerice Sept. 20, 2016

Sept. 20, 2016

Dear all, I have found some severe discrepancies between an objectified tree and its pickle-dump and -loaded cache. It might be reported somewhere but I could not find it. My original issue, if it interests anyone, was found in https://github.com/Capitains/MyCapytain/blob/improvement/buggy.sh as I was benchmarking the effect of pickle. This resulted in pickled object not having the same behavior as the original object (There is a loop in there which checks for sibling to reconstruct a partial tree. Pickled object would not stop "normally" and would get much more that original asked). The issue with the original code, which you can check out, is that it's a "big" codebase and some part of it is undocumented (I unfortunately forgot to document two or three functions as I pushed them and now find myself decrypting it). Most of all, it is a long loop and I am not sure how it would be easy to debug for people. But please if you wish, feel free to do so ;) To show the bug in a limited fashion, in a readable form, I made a repo there : https://github.com/PonteIneptique/test-lxml. It runs on the latest 3.6.4 of LXML on Python 3.5 (did not test on Python 2.7). When I loop over the same tree in three forms different (etree.parse, objectify, pickled objectify) the first and the second are alright but the third shows differences really quick (at a node level). I would love to know if this is an "expected" behavior (ie no focus has been set on checking pickled working, which I would totally understand) or if it is an unknown bug. Best Thibault

2 4