Mailman 3 November 2013 - lxml - The Python XML Toolkit

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

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

April 9, 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. 30, 2022

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

Htmldiff stripping newlines from pre tags
by Raniere Silva Nov. 30, 2013

Nov. 30, 2013

The bug #1206077 was mark as fixed but I found a bug: >>> import lxml.html.diff >>> bug = """<pre>foo ... bar</pre>""" >>> print("Input `bug`:\n{}\nDiff Output `bug`:\n{}".format(bug, ... lxml.html.diff.htmldiff(bug,bug))) Input `bug`: <pre>foo bar</pre> Diff Output `bug`: <pre>foo bar</pre> The diff output should be <pre>foo bar</pre> If any one can give me a tip of what I should do to fix it I will be happy to try. Raniere

1 0

use of libxml2 xmlXPathOrderDocElems routine?
by Paul Tremberth Nov. 26, 2013

Nov. 26, 2013

Hi everyone, I've read in a few places that libxml2's xmlXPathOrderDocElems can help speed up XPath queries when doing read-only lookups on documents. http://www.xmlsoft.org/html/libxml-xpath.html#xmlXPathOrderDocElems Has anyone tried it? Would it make sense to have a method like .xpath_speedup() or something on the _Element class? Perl LibXML has it: http://search.cpan.org/~shlomif/XML-LibXML-2.0107/lib/XML/LibXML/Document.p… Mentioned here: http://code.activestate.com/lists/perl-xml/8161/ > So you see, the greatest performance boost is achieved by indexing > the elements and only after that there is a small but noticable > benefit of pre-compiling the XPath expressions. This Zori project (I know nothing about) is using it: https://www.assembla.com/spaces/Zori/wiki https://www.assembla.com/code/Zori/subversion/nodes/372/trunk/src/ens/ens_r… > ens_read_xml_popen( &doc, &ctx, voff_proc, ens_opt ); > //This supposedly speeds up XPath evaluation for static documents > //Update: not just supposed, but vast improvement for reading (many) walkers > xmlXPathOrderDocElems( ctx->doc ); Regards, Paul.

3 3

Get depth of an element after xpath query
by Bogdan Cristea Nov. 21, 2013

Nov. 21, 2013

Is there a way to obtain the depth of an element after an xpath query ? I am interested in finding the position of an element in a hierarchy of elements.

2 2

lxml.etree.CDATA - different unicode strings map to same XML - is this expected behaviour?
by Dave McKee Nov. 19, 2013

Nov. 19, 2013

[I originally wrote this for StackOverflow, hence all the backticks; I've left them in to deliminate strings.] Not sure if this is a bug or me failing to understand `CDATA`. I have some Python 2 `unicode` objects I want to include in the text of my XML document; I've been asked to put them into `CDATA`, so I used `element.text = lxml.etree.CDATA(mytext)`. However, `þ` (repr: `u'\xfe'`) and `þ` (repr: `u'þ'`) seem to produce the same XML output, despite being very different strings: `<root><![CDATA[þ]]></root>` which lxml parses as `þ`. Can someone confirm it's a bug, or correct my wrongheadedness about using CDATA? BTW: `element.text = mytext` (i.e. no CDATA involved) works as I'd expect. >>> lxml.etree.__version__ u'3.2.4' _test code:_ import lxml.etree import sys literal=sys.argv[1].decode('utf-8') print repr(literal) literalroot=lxml.etree.fromstring("<root></root>") literalroot.text = lxml.etree.CDATA(literal) xml = lxml.etree.tostring(literalroot) print xml print literal, lxml.etree.fromstring(xml).text $ python test.py "þ" u'\xfe' <root><![CDATA[þ]]></root> þ þ $ python test.py "þ" u'þ' <root><![CDATA[þ]]></root> þ þ

2 1

Using lxml with Ubuntu
by Jonathan Gossage Nov. 17, 2013

Nov. 17, 2013

I am trying to use lxml on Ubuntu 13.10 64 bit. I created a virtualenv workspace with Python 3.3.2 64 bit and installed lxml using pip with no reported errors. However when I try to run a Python script with the following code: import lxml context = lxml.etree.iterparse(...) I get the following error: AttributeError: 'module' object has no attribute 'etree' I have verified that the etree .so file is in the site-packages directory of the virtualenv. I tried setting the LD_LIBRARY_PATH environment variable to the site-packages/lxml directory but this did not help. I am at a complete loss to know how to proceed from here.

2 1