Mailman 3 March 2013 - 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

Memory leak when parsing XML files in sequence?
by Maarten van Gompel (proycon) 03 May '13

03 May '13

Hi, I stumbled across what I think it a memory leak within the lxml module. I am parsing literally millions of mostly small XML files, in sequence. In the following, simplified, fashion: index = glob.glob('/path/to/dir/with/huge/number/of/xml/files/*xml') for f in index: d = lxml.etree.parse(f) The problem is that (almost) every iteration, memory usage is increased. But note that d gets overwritten everytime and the reference to the previous document should be lost (I don't reference it anywhere else). Even an explicit 'del d' and gc.collect() within the loop doesn't help to clear up the extra memory. I used objgraph to debug a bit and the Python reference counts remain unchanged as I would expect, leaving me to conclude that this is a memory leak problem in the lxml module. This becomes problematic quickly when dealing with millions of XML files. I attach a short log excerpt in which I extracted resident memory usage from ps after each iteration and measure the increase. Note that I only parse the documents, to be overwritten each time, I don't do anything else with them in this test case. Is this a known problem? Is there anything else I explicitly need to do to free the memory used? The problem does not reproduce if I reload the same document over and over again. Memory usage remains constant then. It only happens when new documents are loaded, and even then in some rare cases the problem dos not occur for some or several iterations, most notably at the start of the log. I also attach an example of an XML file. Python 2.7.2 (ubuntu 11.10, x86_64) lxml.etree : (2, 3, 0, 0) libxml used : (2, 7, 8) libxml compiled : (2, 7, 8) libxslt used : (1, 1, 26) libxslt compiled : (1, 1, 26) Regards, -- Maarten van Gompel (Proycon) E-mail: proycon(a)anaproy.nl Homepage: http://proycon.anaproy.nl Google+: https://plus.google.com/105334152965507305708 Facebook: http://facebook.com/proycon Twitter: http://twitter.com/proycon

6 16

Namespaced attributes losing their namespace
by Tyler Spivey 01 May '13

01 May '13

In the below test script, I'm not getting the result I expect. Is this a bug in lxml? If not, what am I doing wrong? I'm using lxml 3.1.1 on win32, downloaded from PyPi. What I get: <root xmlns="url1"> <test attrib="value"/> </root> I expect attrib to not lose its namespace, as shown when I re-parse the output: >>> lxml.etree.parse('test.xml').getroot()[0].attrib {'attrib': 'value'} If I swap the append and the attribute setting, things work: <test xmlns:ns0="url1" ns0:attrib="value"/> >>> lxml.etree.parse('test.xml').getroot()[0].attrib {'{url1}attrib': 'value'} If this is intended behaviour, I'll have to see how to fit that into my design, since my functions return elements ready for appending. from lxml import etree nsmap = {None: 'url1'} root = etree.Element('{url1}root', nsmap=nsmap) test = etree.Element('{url1}test') test.attrib['{url1}attrib'] = 'value' root.append(test) print etree.tostring(root, encoding='utf-8', pretty_print=True)

2 6

How to pass xmlSaveOption flags to etree.tostring?
by Marcello Perathoner 01 Apr '13

01 Apr '13

I need to serialize XHTML 1.1 without minimized empty elements. Specifically, I want to produce EPUB 2 files, which require XHTML 1.1, but some user agents, like epubreader for firefox, load the XHTML files from disk, whereas firefox uses the HTML parser and makes a big mess of minimized elements. So I wonder if there is a way to pass the option flags in libxml xmlSaveOption to etree.tostring (). In case there is no such way, I humbly request the feature to be added. Regards -- Marcello Perathoner webmaster(a)gutenberg.org

2 5

lxml 3.1.1 released
by Stefan Behnel 29 Mar '13

29 Mar '13

Hi everyone, I just released lxml 3.1.1. This is a pure bug-fix release for the stable 3.1 series. You can get it from PyPI: http://pypi.python.org/pypi/lxml/3.1.1 The documentation is here: http://lxml.de/ Download: http://lxml.de/files/lxml-3.1.1.tgz Signature: http://lxml.de/files/lxml-3.1.1.tgz.asc GitHub: https://github.com/lxml/lxml/commit/98c8562f7d659b49997c136947afdf6bf835d5ab This release was built using Cython 0.18. Note that the build no longer uses Cython, even if it is installed. Recompilation of the sources has to be requested explicitly with the setup.py option "--with-cython". If you are interested in commercial support or customisations for the lxml package, please contact me directly. Have fun, Stefan 3.1.1 (2013-03-29) ================== Features added -------------- Bugs fixed ---------- * LP#1160386: Write access to ``lxml.html.FormElement.fields`` raised an AttributeError in Py3. * Illegal memory access during cleanup in incremental xmlfile writer. Other changes ------------- * The externally useless class ``lxml.etree._BaseParser`` was removed from the module dict.

1 0

Solution for Inkscape osx 10.7 and lxml glitch
by Kurt Olsen 10 Mar '13

10 Mar '13

Well folks, if anybody else comes here complaining about this issue for the osx 10.7.5 Inkscape 48 problem - this worked. Again, thanks for your time... I have written a workaround patch and made it available for download (as part of the Eggbot extensions for Inkscape), for anyone needs a short-term workaround for this issue-- that is, before an official solution is released by the Inkscape developers. You can download it here: http://code.google.com/p/eggbotcode/downloads/detail?name=EggBot2.2.2.r2.mp… Full disclosure: A. This is a totally unofficial hack, not endorsed in any way by the Inkscape developers. :) B. The download is a standard Mac installer package for the Eggbot extensions for Inkscape, which installs the following software: 1) The Eggbot extensions for Inkscape, a set of Inkscape Extensions for creating drawings for and operating an Eggbot, 2) The Hershey Text extension for Inkscape, a "render" extension for drawing stroke-based text, and 3) The patch to Inkscape.app, for version 0.48 and newer, which allows extensions to operate properly under MacOS 10.7. C. This is free software, licensed under the GPL, released in the hopes that it will be helpful, but released strictly on an as-is basis.

1 0