lxml - The Python XML Toolkit July 2021

lxml@python.org

6 participants
10 discussions

[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] 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

Tested value modified in validation error message
by Bob Kline 16 Jul '22

16 Jul '22

Before I file a ticket, I wanted to check here to find out if this is a known problem (I searched the bug tracker, but didn't see any matches). Our customer is using a commercial XML editor and the editor's implementation of the DOM API sometimes garbles whitespace inside text nodes when serializing XML documents for the document's xml property. This causes schema validation errors when we send that serialization off to be validated against the document type's schema using lxml. The problem we have run into with lxml is that the message property of the error object which comes back in the schema object's error_log has altered the value being validated. So, for example, if the text content of an element in the serialized DOM is "Processing\ncomplete" and the value it was supposed to match in the enumerated valid values is "Processing complete" then the message attribute for the corresponding object in the error_log has Element 'ProcessingStatusValue': [facet 'enumeration'] The value 'Processing complete' is not an element of the set {'Ready for English peer review', 'Ready for English scientific review', 'Ready for English OCCM review', 'Ready for Spanish peer review', 'Ready for Spanish OCCM review', 'Ready for publishing', 'Ready for translation', 'Processing complete'}. In effect saying "the value 'Processing complete' does not match the value 'Processing complete'." Took a very long time for us to figure out that the error message was wrong, and that it should have said ... The value 'Processing\ncomplete' is not an element of the set .... -- Bob Kline https://www.rksystems.com mailto:bkline@rksystems.com

4 10

Question - LXML compatibility with Python 3.9 on Linux (travis)
by Petr Hanák 18 Aug '21

18 Aug '21

LXML package states, that has minimal requirements on python - Requires: Python >=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*, != 3.4.* Based on what I see on Travis, it seems to me, that for python 3.9.x. the minimum stable LXML version is 4.3.x; is that expected? Sample log: Collecting lxml==4.2.6 Downloading lxml-4.2.6.tar.gz (2.4 MB) Building wheels for collected packages: lxml Building wheel for lxml (setup.py) ... error ERROR: Command errored out with exit status 1: command: /home/travis/virtualenv/python3.9.1/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-i7un6wlk/lxml_b3782dbd0b1b4611a75033d4ab809f51/setup.py'"'"'; __file__='"'"'/tmp/pip-install-i7un6wlk/lxml_b3782dbd0b1b4611a75033d4ab809f51/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-v441aa6c … … creating build/temp.linux-x86_64-3.9/src/lxml gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -g -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -fPIC -DCYTHON_CLINE_IN_TRACEBACK=0 -I/usr/include/libxml2 -Isrc -Isrc/lxml/includes -I/home/travis/virtualenv/python3.9.1/include -I/opt/python/3.9.1/include/python3.9 -c src/lxml/etree.c -o build/temp.linux-x86_64-3.9/src/lxml/etree.o -w src/lxml/etree.c: In function ‘__Pyx_modinit_type_init_code’: src/lxml/etree.c:230310:32: error: ‘PyTypeObject {aka struct _typeobject}’ has no member named ‘tp_print’ __pyx_type_4lxml_5etree_Error.tp_print = 0; You can see the full logs and which version was installed sucessfully and which not on the compatibility build matrix here: https://app.travis-ci.com/github/SAP/python-pyodata/builds/233333488

2 2

lxml.objectify interprets <x>1000_000</x> as int in Python>3.6 - should it?
by Holger.Joukl＠LBBW.de 13 Aug '21

13 Aug '21

Hi, python2.7 -c 'from lxml import objectify; root = objectify.fromstring("<root><x>1000_000</x></root>"); print(root.x, type(root.x), type(root.x.pyval)); print(root.x.text, type(root.x.text)); print(objectify.dump(root))' ('1000_000', <type 'lxml.objectify.StringElement'>, <type 'str'>) ('1000_000', <type 'str'>) root = None [ObjectifiedElement] x = '1000_000' [StringElement] python3.6 -c 'from pytaf.objectify.xmsg import *; from lxml import etree, objectify; root = objectify.fromstring("<root><x>1000_000</x></root>"); print(root.x, type(root.x), type(root.x.pyval)); print(root.x.text, type(root.x.text)); print(objectify.dump(root))' 1000000 <class 'lxml.objectify.IntElement'> <class 'int'> 1000_000 <class 'str'> root = None [ObjectifiedElement] x = 1000000 [IntElement] According to https://www.w3.org/TR/xmlschema-2/#integer 1000_000 is not a valid integer literal. But it is for Python since 3.6. The magic lxml.objectify type lookup/annotation simple does int(s) and interprets success as "shall be interpreted as int". One could argue that - when parsing XML data - this is not the right/sane/intuitive choice. Or is it? :-) <x>1000_000</x> is not an integer in the XML world. Opinions if that should be changed, maybe switchable? Would it break things for you? Of course, Python 3.6 (and consequently this objectify behavior) is 5 years old now and nobody seemed bothered. Plus you can customize the default lookup mechanism anyway. Cheers, Holger Landesbank Baden-Wuerttemberg Anstalt des oeffentlichen Rechts Hauptsitze: Stuttgart, Karlsruhe, Mannheim, Mainz HRA 12704 Amtsgericht Stuttgart HRA 4356, HRA 104 440 Amtsgericht Mannheim HRA 40687 Amtsgericht Mainz Die LBBW verarbeitet gemaess Erfordernissen der DSGVO Ihre personenbezogenen Daten. Informationen finden Sie unter https://www.lbbw.de/datenschutz.

2 2

[newbie] Removing all elements that match string?
by Gilles 30 Jul '21

30 Jul '21

Hello, I'm only getting started with (l)xml, and was curious to know if someone had an example of how to remove all items in an XML file that match the following string: ^\t*<ele>100.25</ele>\r\n Thank you.

2 2

Is xlC required to build on AIX?
by Albert Vaca Cintora 22 Jul '21

22 Jul '21

Hi, I'm trying to "pip install lxlc" on AIX. Even though I have GCC installed and I have the env var CC pointing to it, the lxml build script is still trying to use xlC and failing because it's not installed. Is xlC a requirement on AIX? This is the error I get: building 'lxml.etree' extension creating build/temp.aix-7.2-2.7 creating build/temp.aix-7.2-2.7/src creating build/temp.aix-7.2-2.7/src/lxml /opt/IBM/xlc/13.1.3/bin/xlc_r -DAIX_GENUINE_CPLUSCPLUS -D_LINUX_SOURCE_COMPAT -q64 -qbitfields=signed -qmaxmem=70000 -qalloca -bmaxdata:0x80000000 -Wl,-brtl -q32 -I/usr/include -I/opt/freeware/include -I/opt/freeware/include/ncurses -DNDEBUG -O2 -DCYTHON_CLINE_IN_TRACEBACK=0 -I/opt/freeware/include/libxml2 -I/opt/freeware/include -Isrc -Isrc/lxml/includes -I/opt/freeware/include/python2.7 -c src/lxml/etree.c -o build/temp.aix-7.2-2.7/src/lxml/etree.o -w unable to execute '/opt/IBM/xlc/13.1.3/bin/xlc_r': No such file or directory Thanks, Albert

1 2

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 July 2021