Mailman 3 December 2016 - lxml - The Python XML Toolkit

[lxml-dev] lxml has its page on launchpad
by Stefan Behnel 11 Apr '23

11 Apr '23

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 10 Apr '23

10 Apr '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/>

6 6

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

Invalid requirement, parse error at "'-===x86-'"
by Ron Gaw <ronmlgaw at yahoo dot com> 30 Dec '16

30 Dec '16

I am getting "Invalid requirement, parse error at "'-===x86-'"from the python2 setup.py install of LXML. Not sure where to go next, can't find anything resembling "'-===x86-'" in requirements.txt or other files in my lxml-3.7.1/ source directory, and not sure what setuptools or other routines would automatically retrieve such a string. My environment / system BASICS: System - MSYS2 / MINGW64 LIBRARY_PATH=C:/msys64/usr/local/lib; INCLUDE_PATH=C:/msys64/usr/local/include; PATH=/mingw64/bin:/usr/local/bin:/usr/bin:/bin:/c/Windows/System32: /c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/\ WindowsPowerShell/v1.0/:/usr/bin/site_perl:/usr/bin/vendor_perl: /usr/bin/core_perl PKG_CONFIG_PATH=/usr/local/lib/pkgconfig CC=/mingw64/bin/x86_64-w64-mingw32-gcc (gcc version is 6.2.0-2) CFLAGS=-I/usr/local/include -O3 msys/python2 2.7.11-1 Next I build / install LXML using the LIBXML2 I've already built previously: $ python2 setup.py build_ext -i -I /usr/local/include/libxml2 Building lxml version 3.7.1. Building without Cython. Using build configuration of libxslt 1.1.29 Building against libxml2/libxslt in one of the following directories: /usr/local/lib C:/msys64/usr/local/lib running build_ext $ python2 setup.py install --record files.txt Building lxml version 3.7.1. Building without Cython. Using build configuration of libxslt 1.1.29 Building against libxml2/libxslt in one of the following directories: /usr/local/lib C:/msys64/usr/local/lib running install ....... <skipping lots of what I think are not relevant outputs....> Processing 3)-x86_64.egg creating /usr/lib/python2.7/site-packages/3)-x86_64.egg Extracting 3)-x86_64.egg to /usr/lib/python2.7/site-packages Adding 3- x86-64 to easy-install.pth file Traceback (most recent call last): File "setup.py", line 233, in <module> **setup_extra_options() File "/usr/lib/python2.7/distutils/core.py", line 151, in setup dist.run_commands() File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands self.run_command(cmd) File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command cmd_obj.run() File "/usr/lib/python2.7/site-packages/setuptools/command/install.py", line 67, in run self.do_egg_install() File "/usr/lib/python2.7/site-packages/setuptools/command/install.py", line 117, in do_egg_install cmd.run() File "/usr/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 391, in run self.easy_install(spec, not self.no_deps) File "/usr/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 621, in easy_install return self.install_item(None, spec, tmpdir, deps, True) File "/usr/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 672, in install_item self.process_distribution(spec, dist, deps) File "/usr/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 697, in process_distribution self.install_egg_scripts(dist) File "/usr/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 575, in install_egg_scripts self.install_wrapper_scripts(dist) File "/usr/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 767, in install_wrapper_scripts for args in ScriptWriter.best().get_args(dist): File "/usr/lib/python2.7/site-packages/setuptools/command/easy_install.py", line 2002, in get_args spec = str(dist.as_requirement()) File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2535, in as_requirement return Requirement.parse(spec) File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2818, in parse req, = parse_requirements(s) File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2762, in parse_requirements req = packaging.requirements.Requirement(line) File "/usr/lib/python2.7/site-packages/pkg_resources/_vendor/packaging/requirements.py", line 94, in __init__ requirement_string[e.loc:e.loc + 8])) pkg_resources._vendor.packaging.requirements.InvalidRequirement: Invalid requirement, parse error at "'-===x86-'" After this error, my site-packages does contain LXML in the following: /msys64/usr/lib/python2.7/site-packages/3\)-x86_64.egg/lxml/ Simple attempts to use LXML fail: $ python2 Python 2.7.11 (default, Mar 4 2016, 10:54:03) [GCC 4.9.2] on msys Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> from lxml import etree Traceback (most recent call last): File "<stdin>", line 1, in <module> File "src/lxml/xmlschema.pxi", line 22, in init lxml.etree (src/lxml/lxml.etree.c:227959) cdef XPath _check_for_default_attributes = XPath( File "src/lxml/xpath.pxi", line 414, in lxml.etree.XPath.__init__ (src/lxml/lxml.etree.c:170395) _XPathEvaluatorBase.__init__(self, namespaces, extensions, File "src/lxml/xpath.pxi", line 133, in lxml.etree._XPathEvaluatorBase.__init__ (src/lxml/lxml.etree.c:166611) self._context = _XPathContext(namespaces, extensions, self._error_log, File "src/lxml/xpath.pxi", line 57, in lxml.etree._XPathContext.__init__ (src/lxml/lxml.etree.c:165567) _BaseContext.__init__(self, namespaces, extensions, error_log, enable_regexp, File "src/lxml/extensions.pxi", line 89, in lxml.etree._BaseContext.__init__ (src/lxml/lxml.etree.c:154495) prefix_utf = self._to_utf(prefix) File "src/lxml/extensions.pxi", line 128, in lxml.etree._BaseContext._to_utf (src/lxml/lxml.etree.c:155101) utf = _utf8(s) File "src/lxml/apihelpers.pxi", line 1443, in lxml.etree._utf8 (src/lxml/lxml.etree.c:31495) raise ValueError( ValueError: All strings must be XML compatible: Unicode or ASCII, no NULL bytes or control characters

1 0

Building lxml and getting its debug symbols (Windows)
by Benoit Bernard 27 Dec '16

27 Dec '16

Hi everyone, I recently had to debug lxml on Windows. Unfortunately, lxml doesn't come shipped with its debug symbols, so my debugger was showing some callstacks with unresolved function names (in libxml2). So I came up with a method to get lxml's debug symbols. I thought that it would be relevant to share it with you, if you ever have to do the same thing. Here's my post with the detailed steps: https://benbernardblog.com/how-to-build-lxml-and-get-its-debug-symbols-on-w… Your feedback is welcome! Benoit

1 0

htmlfile doesn't escape attribute values
by Burak Arslan 27 Dec '16

27 Dec '16

Hello, This is a heads-up for bug 1594155 here: https://bugs.launchpad.net/lxml/+bug/1594155 Please consider the following test case. >>> from lxml import html >>> from lxml.etree import htmlfile >>> from lxml.html.builder import E >>> from StringIO import StringIO >>> out = StringIO() >>> with htmlfile(out) as f: ... with f.element("tagname", attrib={"attr": '"misquoted"'}): ... f.write("foo") ... >>> out.getvalue() '<tagname attr=""misquoted"">foo</tagname>' Expected output: '<tagname attr=""misquoted"">foo</tagname>' Lack of proper escaping confuses the hell out of browsers :) Proper escaping is needed to safely put html documents inside srcdoc attribute of an <iframe>. The workaround is to quote the data before putting it inside an attribute. Fortunately, only replacing " with " is enough and & is also not escaped (but it should be). versions: Python : sys.version_info(major=2, minor=7, micro=11, releaselevel='final', serial=0) lxml.etree : (3, 6, 0, 0) libxml used : (2, 9, 3) libxml compiled : (2, 9, 3) libxslt used : (1, 1, 28) libxslt compiled : (1, 1, 28) Best regards, Burak

1 1

Failed to install lxml on CentOS 6 x64
by 王翌舟 26 Dec '16

26 Dec '16

Hello, I tried to install lxml through pip3, but it failed and threw out error " command 'gcc' failed with exit status 1” (the entire log file is in the attachment). The version of libxml2 is 2.7.6, libxslt is 1.1.26 (both devel version is installed), python is 3.6.0, gcc is 4.4.7. The system is CentOS 6.8 x64 with kernel 2.6.32-642.11.1.el6x86_64. I wonder how to install lxml properly on my server. If you need more information, just send me an email, I’ll reply as soon as possible.Looking forward to your early reply. Best regards. Wade

2 1

manywheel release policy
by Steven Maude 22 Dec '16

22 Dec '16

Hi all, What's lxml's packaging and release policy regarding manylinux wheels? There's a manylinux wheel for 3.6.4 but not 3.7.0. Was this just a trial for 3.6.4? Or an omission when packaging 3.7.0? Asking here because I couldn't find anything about this on the bug tracker (and because it may be a deliberate choice, not a bug). Thanks, Steve

2 1