Mailman 3 August 2011 - 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

[lxml-dev] confusing xpath performance characteristics
by jholg＠gmx.de Aug. 24, 2012

Aug. 24, 2012

Hi, I ran into some performance characteristics of lxml/libxml2 xpath that I find rather confusing: I try to find the @type attribute of a certain element in an XML Schema (which contains lots of complexType definitions with lots of elements in them; unfortunately I can't post the schema): >>> timeit.Timer(stmt="""xpath(schema)""", setup="""from lxml import etree, objectify; schema=etree.parse('NDM.xsd').getroot(); xpath = etree.XPath('//xs:element[@name="equity"]/@type', namespaces={'xs': 'http://www.w3.org/2001/XMLSchema'})""").repeat(number=10) [0.095885038375854492, 0.096823930740356445, 0.096174955368041992] So I think I'm being smart and give a little more path information - reckoning that this should *improve* performance: >>> timeit.Timer(stmt="""xpath(schema)""", setup="""from lxml import etree, objectify; schema=etree.parse('NDM.xsd').getroot(); xpath = etree.XPath('/xs:schema//xs:element[@name="equity"]/@type', namespaces={'xs': 'http://www.w3.org/2001/XMLSchema'})""").repeat(number=10) [0.1770780086517334, 0.1775970458984375, 0.17748594284057617] Hm. Performance degrades slightly. I'm adding even more of the path to where my desired elements live in the schema: >>> timeit.Timer(stmt="""xpath(schema)""", setup="""from lxml import etree, objectify; schema=etree.parse('xsd/NDM.xsd').getroot(); xpath = etree.XPath('/xs:schema/xs:complexType//xs:element[@name="equity"]/@type', namespaces={'xs': 'http://www.w3.org/2001/XMLSchema'})""").repeat(number=10) [103.79744100570679, 103.83671712875366, 103.61817717552185] What??? >>> timeit.Timer(stmt="""xpath(schema)""", setup="""from lxml import etree, objectify; schema=etree.parse('/ae/data/pydev/hjoukl/NDM/SVN_CO/TRUNK/ndm/reference/xsd/NDM.xsd').getroot(); xpath = etree.XPath('/xs:schema/xs:complexType/*/xs:element[@name="equity"]/@type', namespaces={'xs': 'http://www.w3.org/2001/XMLSchema'})""").repeat(number=10) [0.044407129287719727, 0.044126987457275391, 0.044229030609130859] >>> Ok, this version's better than my naive approach, which seems logical to me. But why would '/xs:schema/xs:complexType//xs:element[@name="equity"]/@type' perform drastically slower than '/xs:schema/xs:complexType//xs:element[@name="equity"]/@type' ? libxml2 problem? Running the same xpaths in Oxygen I don't notice performance differences (can't profile this). Holger -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

2 5

[Pull request] Static builds may specify the download directory.
by Laurence Rowe Aug. 31, 2011

Aug. 31, 2011

https://github.com/lxml/lxml/pull/10 Currently static builds look in 'libs' for downloads. This patch makes that directory configurable using the DOWNLOAD_DIR environment variable or the --download-dir= command line option. When using zc.buildout eggs, are built in a temporary directory, making it impossible to supply lxml with the appropriate tarballs. I would rather use the inbuilt static build support rather than resort to z3c.recipe.staticlxml. After downloading the tarballs to the appropriate location, with this change I can now specify: ``` [lxml] recipe = zc.recipe.egg:custom egg = lxml environment = lxml-env [lxml-env] STATIC_DEPS = true DOWNLOAD_DIR = ${buildout:directory}/lxmldownloads LIBXML2_VERSION = 2.7.8 LIBXSLT_VERSION = 1.1.26 LIBICONV_VERSION = 1.14 ``` Laurence

1 0

Module etree syntax error
by Michael McLoughlin Aug. 29, 2011

Aug. 29, 2011

Would someone please explain the following syntax error that appears when importing the etree module: Python 2.7.2 (default, Jun 12 2011, 15:08:59) [MSC v.1500 32 bit (Intel)] on win32 Type "copyright", "credits" or "license()" for more information. >>> from lxml import etree >>> parser = etree.XMLParser() >>> tree = etree.XML("<root></b>", parser) Traceback (most recent call last): File "<pyshell#2>", line 1, in <module> tree = etree.XML("<root></b>", parser) File "lxml.etree.pyx", line 2723, in lxml.etree.XML (src/lxml/lxml.etree.c:52448) File "parser.pxi", line 1573, in lxml.etree._parseMemoryDocument (src/lxml/lxml.etree.c:79932) File "parser.pxi", line 1452, in lxml.etree._parseDoc (src/lxml/lxml.etree.c:78774) File "parser.pxi", line 960, in lxml.etree._BaseParser._parseDoc (src/lxml/lxml.etree.c:75389) File "parser.pxi", line 564, in lxml.etree._ParserContext._handleParseResultDoc (src/lxml/lxml.etree.c:71739) File "parser.pxi", line 645, in lxml.etree._handleParseResult (src/lxml/lxml.etree.c:72614) File "parser.pxi", line 585, in lxml.etree._raiseParseError (src/lxml/lxml.etree.c:71955) XMLSyntaxError: Opening and ending tag mismatch: root line 1 and b, line 1, column 11 -- M McLoughlin “This e-mail is intended for the exclusive use of the individual to whom it is addressed. The information contained herein may be proprietary, confidential, and exempt from disclosure under applicable law. If the reader of this e-mail has received this communication in error, please immediately notify the sender by telephone or by e-mail and destroy this message”

3 2

Dropping Python 2.3 support
by Stefan Behnel Aug. 26, 2011

Aug. 26, 2011

Hi, I'm planning to drop support for CPython 2.3 right in the next release. If anyone feels an urgent need for it to stay supported, please provide a solid line of reasoning in response to this e-mail, preferably accompanied by a funding plan. Basically, CPython 2.3 lacks several features at the language, standard library and C level that make a developer's and distributor's life easier. It was followed by Python 2.4 seven years ago and has not received even security updates for more than three years. There have been seven newer release series of CPython since then, so it's not just resting, it's a truly dead parrot. Stefan

3 3

Parsing HTML
by John Benediktsson Aug. 26, 2011

Aug. 26, 2011

Hi, I have a question about parsing HTML. >>> from lxml.html import fromstring, tostring It parses trailing whitespace in some cases: >>> html = """<div>some <i>text</i> </div>""" >>> html == tostring(fromstring(html)) True But it seems to break when encountering unknown tags (such as the "blah" tag below). >>> html = """<div>some <blah>text</blah> </div>""" >>> html == tostring(fromstring(html)) False How can I fix it to include trailing whitespace for all tags? Thanks, John.

1 0