lxml - The Python XML Toolkit May 2017

lxml@python.org

3 participants
7 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

thread-specific data for xslt callbacks
by Bob Kline 13 Oct '17

13 Oct '17

I need to make some thread-specific data available to my xslt function callbacks. I think I've sort of reverse-engineered a way to do it, by creating my own parser class, stuffing the data I need into an instance of that class, using the parser instance to parse the XSL/T filter, and then in the extension function following the context argument's context_node to its root tree, which in turn gets me back to my own parser object (and my thread-specific data). Is there a more elegant way to do it that I just haven't yet stumbled across in reading through the API docs? Thanks! -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com

2 8

Returning Multiple Schema Errors when Using Iterparse
by Philip Zerull 11 May '17

11 May '17

Hi everyone, So I have to validate vary large xml files (gigabytes large) against xsd schema files. I have been asked to produce line and column numbers where the errors occurred in the file. I'm using: Python 3.5.2 lxml 3.7.3 libxml2 2.9.3+dfsg1-1ubuntu0.2 Ubuntu 16.04 The following code does a good job of getting a list of all the issues with the xml file that I can nicely present to the user (for brevity I left out a bunch of try/catch statements). This works great because it also gives the line and column numbers in the xml file where the issues occurred: schema_root = etree.XML(xsd_file.read()) schema = etree.XMLSchema(schema_root) parser = etree.XMLParser(schema=schema) parsed_xml = etree.XML(xml_file.read()) if not schema.validate(parsed_xml): errors_list = schema.errors_log Unfortunately, this results in reading the entire file in memory. Alternatively, I can do the following: schema_root = etree.XML(xsd_file.read()) schema = etree.XMLSchema(schema_root) for event, elem in etree.iterparse(xml_file, schema=schema): #clear stuff from memory elem.clear() parent = elem.getparent() while elem.getprevious() is not None: del elem.getparent()[0] If the xml fails to validate against the xsd file then the iterator returned by etree.iterparse's next method raises an etree.XMLSyntaxError for the first xsd issue it finds. This does a great job of keeping the memory usage constant over even very large files, but it only tells me if the xsd file is valid or not. It does not give me a list of issues like the previously mentioned method does. I tried just catching the XMLSyntaxError by surrounding only the iterator's next method with a try/catch and attempting to move on with the file even if the error was raised, but that just resulted in an infinite loop where the iterator's next method continuously raised the same error for the same element and stopped progressing through the file. It's very tempting to think that there must be a way to get the best of both worlds here, but I've scoured the documentation, tried a few things, as well as briefly dug into the code a bit but I haven't had any luck yet. I'm not even sure doing this would be possible using iterparse. Any advice in this area would be greatly appreciated. Regards, Phil Zerull

2 2

Problems with v3.7.3 for Python 2.7 and apache wsgi_mod
by EricWentz＠Eaton.com 08 May '17

08 May '17

Hello lxml version 3.7.3 crashes my apache instance with a segmentation fault - does not crash with 3.7.0, but 3.7.0 does not appear to work correctly behind my web proxy. Has anybody else seen this behavior? Is there currently a bug submitted for this? Thanks Eric

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 May 2017