Mailman 3 January 2014 - lxml - The Python XML Toolkit

Re: [lxml] lxml.etree.XMLSyntaxError: Char 0x0 out of allowed range...
by Stefan Behnel Jan. 16, 2014

Jan. 16, 2014

Jose Soares, 19.12.2013 16:32: > On 12/19/2013 04:23 PM, Stefan Behnel wrote: >> import lxml.etree as et >> >>>et.fromstringlist('<?xml version="1.0" ?><test/>') > > using fromstring raises this error too: > > print etree.fromstring(result) > File "lxml.etree.pyx", line 2743, in lxml.etree.fromstring > (src/lxml/lxml.etree.c:52665) > File "parser.pxi", line 1564, in lxml.etree._parseMemoryDocument > (src/lxml/lxml.etree.c:79843) > ValueError: Unicode strings with encoding declaration are not supported. That means that you passed in a Unicode string (it seems that the Suds class is a subtype of Unicode), but one that says it's *not* Unicode, i.e. that it is actually an encoded string. The example you gave started like this: """ <?xml version="1.0" encoding="UTF-8"?>... """ So the string says it's UTF-8 encoded, but it's actually not. lxml rejects that explicitly. The solution is to pass in a byte string instead. Not sure if Suds has a way to get one. And you didn't say anything about how you get that string in the first place. > print etree.fromstringlist(str(result)) > > <Element RISPOSTA at 0x1bee320> I've added a sanity check to prevent this. You'll get a ValueError now. My guess is that the original problem was character by character parsing of Unicode strings. And who would want to do that in the first place... Stefan

1 0

segfault possibly python-lxml, libxml2 related
by Matt Baker Jan. 15, 2014

Jan. 15, 2014

Hi all, First off, I must admit limited abilities with debugging segfaults, so apologies for that. I run a configuration management server bcfg2 which is python based heavily utilising python-lxml. The server runs debian wheezy (recently squeeze which exhibited the problem too). It appears on the face of it that it's segfaulting during a python genshi template which reads in some XML. Please see the gdb analysis attached. Any advice or pointers or next steps in how to determine the cause of the segfault would be greatly appreciated. Thanks in advance. Matt -- Matthew Baker :: Unix/Security Team Lead Infrastructure, Systems and Operations @University of Bristol Team email: it-sysops(a)bristol.ac.uk Tel: +44(0)117 3317467 Add: Uni of Bristol, Computer Centre, Tyndal Ave, Bristol. BS8 1UD

2 6

lxml 3.3.0 beta 4 released
by Stefan Behnel Jan. 12, 2014

Jan. 12, 2014

Hi all, I just released the fourth and last beta of lxml 3.3.0, containing some bug fixes and preliminary support for Python 3.4 (by building with Cython 0.20pre). The final release is expected as soon as Cython 0.20 is released, hopefully in a couple of days. Please give it all the testing you can afford, especially for the new iterparse() and pull parser code, and also on the more exotic platforms like Windows. The documentation is here: http://lxml.de/ Download: http://lxml.de/files/lxml-3.3.0beta4.tgz Signature: http://lxml.de/files/lxml-3.3.0beta4.tgz.asc Changelog: http://lxml.de/3.3/changes-3.3.0beta4.html Github: https://github.com/lxml/lxml/commit/dd0bbe36408fe1a49f278f368e8e76aff8e075bf This release was built using Cython 0.20pre, gitrev 012ae82eb. If you are interested in commercial support or customisations for the lxml package, please contact me directly. Have fun, Stefan 3.3.0beta4 (2014-01-12) ======================= Features added -------------- Bugs fixed ---------- * The (empty) value returned by the ``attrib`` property of Entity and Comment objects was mutable. * Element class lookup wasn't available for the new pull parsers or when using a custom parser target. * Setting Element attributes on instantiation with both the ``attrib`` argument and keyword arguments could modify the mapping passed as ``attrib``. * LP#1266171: DTDs instantiated from internal/external subsets (i.e. through the docinfo property) lost their attribute declarations. Other changes ------------- * Built with Cython 0.20pre (gitrev 012ae82eb) to prepare support for Python 3.4.

1 0

etree.iterparse (3.2.3) with set_element_class_lookup()
by Herm Fischer Jan. 9, 2014

Jan. 9, 2014

Hi, I'm trying (with 3.2.3) to use iterparse with set_element_class_lookup but it doesn't seem to be effective (it's inherited but not described to be operable). Is it supposed to work? (The workaround for now is too slow, use start and end events to build a separate tree from a parser implementing the class lookup. And of course the 3.3 beta Pull parser looks like a better solution for the future when Windows distributions become available for 3.3) Herm Fischer

2 2

Building 3.3.0beta3 on Windows vs Linux
by Herm Fischer Jan. 9, 2014

Jan. 9, 2014

2 2

how to get xpath to a value
by Vincent Davis Jan. 4, 2014

Jan. 4, 2014

Is it possible to get the xpath to a value in an html document. That is for example, if I know "apple" is in an html document how can I get the xpath to "apple" "apple" may occur more than once in the html in which case, I would expect that I would get somthing like a list of xpaths Vincent Davis 720-301-3003

3 2

lxml 3.3.0 beta 3 released
by Stefan Behnel Jan. 2, 2014

Jan. 2, 2014

Hi all, I just released the third (and hopefully last) beta of lxml 3.3.0, containing some major bug fixes and optimised Unicode string parsing code for Python 3.3. Please give it all the testing you can afford, especially for the new iterparse() code. The documentation is here: http://lxml.de/ Download: http://lxml.de/files/lxml-3.3.0beta3.tgz Signature: http://lxml.de/files/lxml-3.3.0beta3.tgz.asc Changelog: http://lxml.de/3.3/changes-3.3.0beta3.html Github: https://github.com/lxml/lxml/commit/ This release was built using Cython 0.19.2. If you are interested in commercial support or customisations for the lxml package, please contact me directly. Have fun, Stefan 3.3.0beta3 (2014-01-02) ======================= Features added -------------- * Unicode string parsing was optimised for Python 3.3 (PEP 393). Bugs fixed ---------- * HTML parsing of Unicode strings could misdecode the input on some platforms. * Crash in xmlfile() when closing open elements out of order in an error case.

1 1

lxml 3.2.5 released
by Stefan Behnel Jan. 2, 2014

Jan. 2, 2014

Hi everyone, I released lxml 3.2.5 as a bug-fix release for the stable 3.2 release series. This release fixes three crash bugs, so upgrading is recommended. You can get it from PyPI: http://pypi.python.org/pypi/lxml/3.2.5 The documentation is here: http://lxml.de/ Download: http://lxml.de/files/lxml-3.2.5.tgz Signature: http://lxml.de/files/lxml-3.2.5.tgz.asc Changelog: http://lxml.de/3.2/changes-3.2.5.html GitHub: https://github.com/lxml/lxml/commit/4bbc11f847dfc30c783c0d54103efe37ebaa090d This release was built using Cython 0.19.2. Note that the build no longer uses Cython, even if it is installed. Recompilation of the sources has to be requested explicitly with the setup.py option "--with-cython". If you are interested in commercial support or customisations for the lxml package, please contact me directly. Have fun, Stefan 3.2.5 (2014-01-02) ================== Bugs fixed ---------- * Crash in xmlfile() when closing open elements out of order in an error case. * Crash in target parsing with attributes. * LP#1255132: crash when trying to run validation over non-Element (e.g. comment or PI).

1 0

Segfault regression with feed parser going from 3.2.1 to 3.2.4
by Phil Mayers Jan. 2, 2014

Jan. 2, 2014

All, I'm running Fedora 18, Python 2.7.3. I've just upgraded my machine and python-lxml has been bumped to 3.2.4, and the test script here: https://gist.github.com/philmayers/046f5f91bdcb9738d57f ...now segfaults. Confirmed working if I roll back to 3.2.1. A colleague reports it works under 3.3.0b2, but I can't test that on the machine I'm on.

2 3

Issue with _IncrementalFileWriter._handle_error
by Burak Arslan Jan. 2, 2014

Jan. 2, 2014

Hi, (I'm working on getting lxml incremental writer to write on a twisted http request object) This is from lxml trunk, _IncrementalFileWriter in serializer.pxi cdef _handle_error(self, int error_result): if error_result != xmlerror.XML_ERR_OK: if self._writer is not None: self._writer._exc_context._raise_if_stored() _raiseSerialisationError(error_result) I could be wrong but I don't think _IncrementalFileWriter should have a separate _writer attribute. Here's the relevant bit of traceback i'm getting: File "serializer.pxi", line 637, in lxml.etree.xmlfile.__exit__ (src/lxml/lxml.etree.c:110916) File "serializer.pxi", line 870, in lxml.etree._IncrementalFileWriter._close (src/lxml/lxml.etree.c:114606) File "serializer.pxi", line 874, in lxml.etree._IncrementalFileWriter._handle_error (src/lxml/lxml.etree.c:114663) Is this a typo/bug or am I missing something? Best, Burak

2 7