lxml - The Python XML Toolkit November 2016

lxml@python.org

4 participants
9 discussions

[lxml-dev] Checking whether a node is a comment/element
by Geoffrey Sneddon 11 Jan '23

11 Jan '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/>

4 4

[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] lxml has its page on launchpad
by Stefan Behnel 21 Sep '22

21 Sep '22

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

3 2

[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

htmlfile doesn't escape attribute values
by Burak Arslan 27 Dec '16

27 Dec '16

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

Re: [lxml] Memory leak when parsing XML files in sequence?
by Benoit Bernard 04 Dec '16

04 Dec '16

In-Reply-To=<4EA045E4.9020508(a)anaproy.nl> Has there been any advancements regarding this memory leak? I built the newest version of lxml (as well as its dependencies) and the problem is still there. I was able to track it down using umdh on Windows: etree!xmlDictLookup+0000025E (c:\tmp\libxml2-win-binaries\libxml2\dict.c, 933) etree!xmlHashAddEntry3+00000053 (c:\tmp\libxml2-win-binaries\libxml2\hash.c, 532) etree!xmlHashAddEntry+00000014 (c:\tmp\libxml2-win-binaries\libxml2\hash.c, 377) etree!xmlAddID+0000011D (c:\tmp\libxml2-win-binaries\libxml2\valid.c, 2632) etree!xmlSAX2AttributeInternal+0000078A (c:\tmp\libxml2-win-binaries\libxml2\sax2.c, 1411) etree!xmlSAX2StartElement+000002AE (c:\tmp\libxml2-win-binaries\libxml2\sax2.c, 1743) etree!htmlParseStartTag+00000579 (c:\tmp\libxml2-win-binaries\libxml2\htmlparser.c, 3926) etree!htmlParseElementInternal+00000069 (c:\tmp\libxml2-win-binaries\libxml2\htmlparser.c, 4467) etree!htmlParseContentInternal+000003D3 (c:\tmp\libxml2-win-binaries\libxml2\htmlparser.c, 4652) etree!htmlParseDocument+000002A2 (c:\tmp\libxml2-win-binaries\libxml2\htmlparser.c, 4818) etree!htmlDoRead+00000094 (c:\tmp\libxml2-win-binaries\libxml2\htmlparser.c, 6786) etree!htmlCtxtReadMemory+00000093 (c:\tmp\libxml2-win-binaries\libxml2\htmlparser.c, 7072) etree!__pyx_f_4lxml_5etree_11_BaseParser__parseUnicodeDoc+0000028A (c:\tmp\lxml-3.6.4\src\lxml\lxml.etree.c, 109222) etree!__pyx_f_4lxml_5etree__parseDoc+0000041F (c:\tmp\lxml-3.6.4\src\lxml\lxml.etree.c, 115220) etree!__pyx_f_4lxml_5etree__parseMemoryDocument+000000E6 (c:\tmp\lxml-3.6.4\src\lxml\lxml.etree.c, 116674) etree!__pyx_pf_4lxml_5etree_22fromstring+00000086 (c:\tmp\lxml-3.6.4\src\lxml\lxml.etree.c, 77737) etree!__pyx_pw_4lxml_5etree_23fromstring+00000294 (c:\tmp\lxml-3.6.4\src\lxml\lxml.etree.c, 77687) python33!PyCFunction_Call+000000F3 (c:\users\martin\33.amd64\python\objects\methodobject.c, 84) python33!PyObject_Call+00000061 (c:\users\martin\33.amd64\python\objects\abstract.c, 2036) python33!ext_do_call+00000295 (c:\users\martin\33.amd64\python\python\ceval.c, 4381) python33!PyEval_EvalFrameEx+00002041 (c:\users\martin\33.amd64\python\python\ceval.c, 2723) python33!PyEval_EvalCodeEx+0000065C (c:\users\martin\33.amd64\python\python\ceval.c, 3436) python33!function_call+0000015D (c:\users\martin\33.amd64\python\objects\funcobject.c, 639) python33!PyObject_Call+00000061 (c:\users\martin\33.amd64\python\objects\abstract.c, 2036) python33!ext_do_call+00000295 (c:\users\martin\33.amd64\python\python\ceval.c, 4381) python33!PyEval_EvalFrameEx+00002041 (c:\users\martin\33.amd64\python\python\ceval.c, 2723) python33!PyEval_EvalCodeEx+0000065C (c:\users\martin\33.amd64\python\python\ceval.c, 3436) python33!fast_function+0000014D (c:\users\martin\33.amd64\python\python\ceval.c, 4168) python33!call_function+00000339 (c:\users\martin\33.amd64\python\python\ceval.c, 4088) python33!PyEval_EvalFrameEx+00001F98 (c:\users\martin\33.amd64\python\python\ceval.c, 2681) For reference, here are my version numbers: Python : sys.version_info(major=3, minor=3, micro=5, releaselevel='final', serial=0) lxml.etree : (3, 6, 4, 0) libxml used : (2, 9, 4) libxml compiled : (2, 9, 4) libxslt used : (1, 1, 29) libxslt compiled : (1, 1, 29) Should I open a new bug? Thanks! Benoit Bernard https://benbernardblog.com

3 3

Re: [lxml] Memory leak when parsing XML files in sequence?
by Benoit Bernard 23 Nov '16

23 Nov '16

1 0

XML schema validation error using 3.6.3
by Tom Kralidis 05 Nov '16

05 Nov '16

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

htm.fromstring rogue parents
by Burak Arslan 03 Nov '16

03 Nov '16

Hello, Perhaps that's a very basic question, but I couldn't find the answer. lxml.html.fromstring adds implicit parents to the parsed element. >>> from lxml import html >>> html.fragment_fromstring("<div>foo</div>").getroottree().getroot() <Element html at 0x7f8a538c1ec0> >>> html.fragment_fromstring("<div>foo</div>").getparent() <Element body at 0x7f8a538c1e10> >>> How do I prevent this? ie I want .getparent() to return None and .getroottree().getroot() to return the top-level element. Best, Burak -- Python : sys.version_info(major=2, minor=7, micro=12, releaselevel='final', serial=0) lxml.etree : (3, 6, 4, 0) libxml used : (2, 9, 4) libxml compiled : (2, 9, 4) libxslt used : (1, 1, 29) libxslt compiled : (1, 1, 29)

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

lxml - The Python XML Toolkit November 2016