lxml - The Python XML Toolkit January 2017

lxml@python.org

11 participants
17 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

etree.cpython-34m.so: undefined symbol: PyExc_SystemError
by Финковский Игорь 17 Feb '17

17 Feb '17

2 1

Lxml test issue in Oracle Solaris
by Esha Wang 17 Feb '17

17 Feb '17

Hello, I am representing Oracle, and currently working on upgrading pylxml in Solaris. We have encountered an issue while running test.py, where cov.xml_report() and cov.html_report() are generating a syntax error in lxml.etree.pyx. coverage.misc.NotPython: Couldn't parse '$(SOURCE_DIR)/src/lxml/lxml.etree.pyx' as Python source: 'invalid syntax' at line 44 Line 44 of lxml.etree.pyx is "cimport cython", and test.py does not seem to be recognizing it. We have checked that valid python (2.7.12) and cython (0.25.1) versions are being used. For now, we have created the following patch, which suppresses the error: --- lxml-3.6.4/test.py_orig 2017-01-11 14:03:08.523061540 +0000 +++ lxml-3.6.4/test.py 2017-01-11 14:03:27.417867156 +0000 @@ -606,14 +606,6 @@ walker = os.path.walk walker(os.path.abspath(cfg.basedir), add_file, None) - try: - cov.xml_report(modules, outfile='coverage.xml') - if cfg.coverdir: - cov.html_report(modules, directory=cfg.coverdir) - finally: - # test runs can take a while, so at least try to print something - cov.report() - # That's all if success: return 0 Additional info below: >>> print("%-20s: %s" % ('Python', sys.version_info)) Python : sys.version_info(major=2, minor=7, micro=12, releaselevel='final', serial=0) >>> print("%-20s: %s" % ('lxml.etree', etree.LXML_VERSION)) lxml.etree : (3, 6, 4, 0) >>> print("%-20s: %s" % ('libxml used', etree.LIBXML_VERSION)) libxml used : (2, 9, 4) >>> print("%-20s: %s" % ('libxml compiled', etree.LIBXML_COMPILED_VERSION)) libxml compiled : (2, 9, 4) >>> print("%-20s: %s" % ('libxslt used', etree.LIBXSLT_VERSION)) libxslt used : (1, 1, 28) >>> print("%-20s: %s" % ('libxslt compiled', etree.LIBXSLT_COMPILED_VERSION)) libxslt compiled : (1, 1, 28) Please let us know if there is additional information we can provide. Thank you, Esha Wang

2 1

`html.make_links_absolute' Ignores `resolve_base_href' Argument
by Sam Davis 17 Feb '17

17 Feb '17

Hi, I'm wanting to use `html.make_links_absolute' [0] with a specific `base_url', which I believe should be possible. With that in mind, I have set the `resolve_base_href' argument to `False'. However, if `<base href=$URL>' tags are present in the document, it uses $URL rather than the given`base_url'. See linked code [1] for an example. I believe this occurs as follows: - `make_links_absolute' final call is to `rewrite_links' with one argument, the `link_repl' function. [2] - `rewrite_links' has `resolve_base_href=True' as a default, so it calls `resolve_base_href'. [3] - `resolve_base_href' then finds the base `tag in the document, and apply its values to all links found in the document'. [4] I think a solution would be to pass the `resolve_base_href' parameter through when `make_links_absolute' calls `resolve_base_href'. Can anyone confirm or correct my logic? Should I report it as a bug? Thanks, Sam [0] https://github.com/lxml/lxml/blob/572e10843774a5d6300125d89bdc423d53c92971/… [1] http://pastebin.com/UFKj6VsQ [2] https://github.com/lxml/lxml/blob/572e10843774a5d6300125d89bdc423d53c92971/… [3] https://github.com/lxml/lxml/blob/572e10843774a5d6300125d89bdc423d53c92971/… [4] https://github.com/lxml/lxml/blob/572e10843774a5d6300125d89bdc423d53c92971/…

2 1

ElementTree.write() and doctype
by Steven Vereecken 22 Jan '17

22 Jan '17

Hi, I was looking for a way to specify a doctype with the write() method of an elementtree, analogous to the "doctype" argument for etree.tostring(). There seems to be no documented way to do so, but I found an (undocumented) argument called "docstring" (instead of "doctype") that seems to work just fine. Should this be renamed to "doctype" and added to the documentation, or is there a reason why it was left out and shouldn't be used? greetings, Steven

3 3

Type attributes with E-factory
by Richard Wellum 17 Jan '17

17 Jan '17

Hi, Sorry for the very basic question. I'm trying lxml for the first time, playing with the builder and I would like to know if it's possible to create type attributes in the top level? E.g: <domain *type='kvm' id='19'*> <name>mcontroller</name> <uuid>9b9e2237-fff5-4598-92ec-89603e4c300a</uuid> </domain> I can't figure out how to add " *type='kvm' id='19'*" to the *domain *above. Something like: controller = E.domain((type='kvm', id='19') E.name('mcontroller'), ... Thanks, ||Rich

2 2

etree.cpython-34m.so: undefined symbol: PyExc_SystemErro
by Финковский Игорь 14 Jan '17

14 Jan '17

REPEAT without HTML ___________________________________________________________ Good afternoon everyone. Sorry for the mistakes English is not my native. Could you help to solve the following problem: in the corporate web server runs the Python interpreter. When I execute the following code in it from lxml import etree error occurs /usr/lib64/python3.4/site-packages/lxml/etree.cpython-34m.so: undefined symbol: PyExc_SystemError But the same code works in IDLE for example. After talking with colleagues I realized that the error occurs because the lxml library does not have libpython.so in the list of dependencies. Could it be? how to rebuild specifying this dependency? I work on CentOS7 x64 python34 x86_64 from lxml import etree print("%-20s: %s" % ('Python', sys.version_info)) Python : sys.version_info(major=3, minor=4, micro=5, releaselevel='final', serial=0) print("%-20s: %s" % ('lxml.etree', etree.LXML_VERSION)) lxml.etree : (3, 7, 2, 0) print("%-20s: %s" % ('libxml used', etree.LIBXML_VERSION)) libxml used : (2, 9, 3) print("%-20s: %s" % ('libxml compiled', etree.LIBXML_COMPILED_VERSION)) libxml compiled : (2, 9, 3) print("%-20s: %s" % ('libxslt used', etree.LIBXSLT_VERSION)) libxslt used : (1, 1, 29) Показать цитату целикомПоказать всю переписку libxslt compiled : (1, 1, 29) -- С уважением, Игорь Финковский +7 (909) 256-90-45 89092569045(a)ya.ru

2 1

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 January 2017