lxml - The Python XML Toolkit October 2014

lxml@python.org

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

Generating code from schema
by Charlie Clark 29 Jan '15

29 Jan '15

Hi, just a quick question about what you can and cannot do with lxml's schema support. In openpyxl we're moving towards a 1:1 implementation of the underlying schema. lxml.objectify isn't directly an option for two reasons: lxml is an optional dependency and there are cases where we'd definitely run out of memory. Instead we're using descriptors to enforce type definitions. This means a little more code but now that it seems to be working well I was thinking whether we could automate some of the process. I've looked at some of the existing XSD to Python generators but the generated code is far from what I'd like to have. Can we use the lxml schema support for anything other than validation? ie. can I query a schema object for a particular definition? Or is the best approach to parse the XSD files directly and work through the definitions with a mapping? Charlie -- Charlie Clark Managing Director Clark Consulting & Research German Office Kronenstr. 27a Düsseldorf D- 40217 Tel: +49-211-600-3657 Mobile: +49-178-782-6226

4 13

Crash on MacOS-X when importing tkinter
by Stefan Behnel 01 Nov '14

01 Nov '14

Hi, I got a crash report when importing tkinter and lxml together under MacOS-X. https://bugs.launchpad.net/lxml/+bug/1384102 Could other Apple users please try the following couple of commands and report if they trigger a crash for them or not? """ import tkinter from lxml import etree print("%-20s: %s" % ('Python', sys.version_info)) print("%-20s: %s" % ('lxml.etree', etree.LXML_VERSION)) print("%-20s: %s" % ('libxml used', etree.LIBXML_VERSION)) print("%-20s: %s" % ('libxml compiled', etree.LIBXML_COMPILED_VERSION)) print("%-20s: %s" % ('libxslt used', etree.LIBXSLT_VERSION)) print("%-20s: %s" % ('libxslt compiled', etree.LIBXSLT_COMPILED_VERSION)) root = etree.Element('test') xml = etree.tostring(root) # <- crashing here """ Please report the library versions that you are using (printed above) and whether it's a static lxml build or links dynamically against libxml2. If someone has gdb available and can provide further information about the spot in libxml2 where this crashes, I'd be happy to hear them. Thanks! Stefan

1 1

XMLParser mode resolve_entities=False and entities in attributes
by jens quade 31 Oct '14

31 Oct '14

Hi, this has been discussed before in 11/2009, but the bug seems to persist, so I will try to document it again: If an XML parser is generated with XMLParser(resolve_entities=False), and the document used declares an external DTD, then entities in attributes are inserted into the parent element (if a parent element exists) directly before the element containing that attribute. Expected behaviour: - an error, because entities are undeclared; or, more useful in some cases: - Entities stay in their attributes Workarounds: - Declare an internal DTD that defines all entities - Use an actual external DTD *and* use dtd_validation=True with XMLParser Sample code: (see also: http://pastebin.com/24bM98La -- some more examples there) from lxml import etree parser = etree.XMLParser(resolve_entities=False) try: tree = etree.XML("""<test>1<a href="übel">ö</a></test>""", parser=parser) except etree.XMLSyntaxError as e: print e Output: > Entity 'uuml' not defined, line 1, column 23 from lxml import etree parser = etree.XMLParser(resolve_entities=False) try: tree = etree.XML("""<!DOCTYPE test SYSTEM ""><test>1<a href="übel">ö</a></test>""", parser=parser) print tree[:] print tree.find('.//a').attrib['href'] print etree.tostring(tree) except etree.XMLSyntaxError as e: print e Output: > [ü, <Element a at 0x1073be3f8>] > bel > <test>1ü<a href="bel">ö</a></test> Tested with various lxml versions, e.g.: Python : sys.version_info(major=2, minor=7, micro=5, releaselevel='final', serial=0) lxml.etree : (3, 4, 0, 0) libxml used : (2, 9, 2) libxml compiled : (2, 9, 2) libxslt used : (1, 1, 28) libxslt compiled : (1, 1, 28) jens

2 1

building lxml with pypy: "pyconfig.h" not found
by Felix Schwarz 27 Oct '14

27 Oct '14

Hi, I just tried to build lxml 3.4.0 using pypy 2.2.1 (on Fedora 20) build failed due to a missing pyconfig.h. Is that expected behavior? I see that there are passing travis builds for the github version so it should be possible somehow. I'm not sure where to start debugging the issue as it could be a lxml problem, pypy error or Fedora packaging bug so I decided to start at the source :-) I started out with the lxml 3.4.0 tar.gz from pypi because I tried to avoid rebuilding all the cython stuff. Maybe that's the problem? $ pypy setup.py build Building lxml version 3.4.0. Building without Cython. Using build configuration of libxslt 1.1.28 Building against libxml2/libxslt in the following directory: /usr/lib64 /usr/lib64/pypy-2.2.1/lib-python/2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'bugtrack_url' warnings.warn(msg) running build running build_py copying src/lxml/includes/lxml-version.h -> build/lib.linux-x86_64-2.7/lxml/includes running build_ext building 'lxml.etree' extension cc -O2 -fPIC -Wimplicit -I/usr/include/libxml2 -I/home/fs/code/szoska/fiverx/lxml-3.4.0/src/lxml/includes -I/home/fs/code/szoska/fiverx/venv.pypy/include -c src/lxml/lxml.etree.c -o build/temp.linux-x86_64-2.7/src/lxml/lxml.etree.o -w src/lxml/lxml.etree.c:8:22: fatal error: pyconfig.h: No such file or directory #include "pyconfig.h" ^ compilation terminated. error: command 'cc' failed with exit status 1 BUT: $ rpm -q --list pypy-devel | grep pyconfig.h /usr/lib64/pypy-2.2.1/include/pyconfig.h Thanks, fs

2 4

Issue writing with 3.4 at python 3.2 at windows
by Pegerto Fernández 03 Oct '14

03 Oct '14

Hello Team, I try to use lxml to perform a c14n over a document c14ndoc = io.StringIO() tree.write_c14n(c14ndoc) I am having this issue: tree.write_c14n(c14ndoc) File "lxml.etree.pyx", line 2271, in lxml.etree._ElementTree.write_c14n (src\lxml\lxml.etree.c:60874) File "serializer.pxi", line 592, in lxml.etree._tofilelikeC14N (src\lxml\lxml.etree.c:124249) File "lxml.etree.pyx", line 316, in lxml.etree._ExceptionContext._raise_if_stored (src\lxml\lxml.etree.c:10291) File "serializer.pxi", line 407, in lxml.etree._FilelikeWriter.write (src\lxml\lxml.etree.c:121770) TypeError: string argument expected, got 'bytes' Do you have any idea ?

2 1

missing void elements
by Burak Arslan 03 Oct '14

03 Oct '14

Hello, Where's the lxml issue tracker? I couldn't find it? Void elements are html tags that don't need a closing tag. is a well known example: >>> from lxml.builder import E >>> html.tostring(E.br()) ' ' >>> etree.tostring(E.br()) ' ' >>> is not a void element, so: >>> html.tostring(E.p()) '' >>> etree.tostring(E.p()) '' see the full list: http://www.w3.org/TR/html5/syntax.html#elements-0 While working on etree.htmlfile, I noticed that the following tags are not treated as void: embed, keygen, source, track, wbr see: https://github.com/lxml/lxml/pull/142#issuecomment-55588559 because of this, lxml can produce invalid html. once this issue is resolved, the tuple at: https://github.com/lxml/lxml/commit/c039e03798d84ac3f897354f0780f15346da136… needs to be updated. best, burak

3 7

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 October 2014