Mailman 3 September 2014 - lxml - The Python XML Toolkit

(no subject)
by Patrick Asselman 23 Sep '14

23 Sep '14

Can somebody please shed some light on what is going on here? Lxml seems to be installed according to pip: $ pip freeze lxml==3.4.0 But for some reason it is not found by Python: $ python3 Python 3.4.0 (v3.4.0:04f714765c13, Mar 15 2014, 23:02:41) [GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import lxml Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: No module named 'lxml' >>> Also help('modules') doesn't show lxml in the list. This is on OSX 10.9.5 Before this, I install py34-lxml through macports and it said "Installing py34-lxml @3.3.5_0", which made me think it was installing an older version, so I chose to uninstall and use pip instead. Pip completes the installation succesfully, but the module cannot be found by Python. Any suggestions? Best regards, Patrick

2 4

I'm an idiot, please help me! ;-)
by Charlie Clark 20 Sep '14

20 Sep '14

Hi, I'm trying to build lxml from source on Mac OS (it builds fine as a dependency) but I seem to be hitting a wall: Trying to build without Cython, but pre-generated 'src/lxml/lxml.etree.c' I get this whether or not I'm using Cython (it's installed) or python setup.py build --static-deps libxml2 and libxlst are installed. Charlie -- Charlie Clark Kronenstr. 27a Düsseldorf D- 40217 Tel: +49-211-938-5360 Mobile: +49-178-782-6226

2 2

Comparing XML requires unicode?
by Charlie Clark 11 Sep '14

11 Sep '14

Hi, last year Stefan very kindly showed me how to use LXMLOutputchecker to compare XML trees. This is a lifesaver if you generate a lot of XML and want to check it: we're using it extensively in openpyxl. But recently I've found myself bashing my head against it repeatedly as it seems to work with unicode only, which means I can't simply use compare_xml(tostring(tree), expected) - wrapper function from https://bitbucket.org/openpyxl/openpyxl/src/03cb2a7f046d02ec3a19cbeba4375b6… I can work around this using a helper function or lxml's handy tounicode(), except that we also need to run tests assuming lxml is not installed. Am I missing something simple? 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

2 2

lxml 3.4.0 released
by Stefan Behnel 10 Sep '14

10 Sep '14

Hi all, I just released the final version of lxml 3.4, with no code changes since the last beta. This is a feature release that mostly cleans up some prior deficiencies and speeds up parsing for documents that contain XML-IDs. Note that this release drops support for older Python versions and now requires Py2.6/7 or Py3.2+. It also removes support for very old versions of libxml2 and libxslt (<=2008). The documentation is here: http://lxml.de/ Download: http://lxml.de/files/lxml-3.4.0.tgz Signature: http://lxml.de/files/lxml-3.4.0.tgz.asc Changelog: http://lxml.de/3.4/changes-3.4.0.html Github: https://github.com/lxml/lxml/blob/14505bc62f5f1fc9fb0ff007955f3e67ab4562bb This release was built using Cython 0.21, but should also build fine with 0.20.x. If you are interested in commercial support or customisations for the lxml package, please contact me directly. Have fun, Stefan 3.4.0 (2014-09-10) ================== Features added -------------- * ``xmlfile(buffered=False)`` disables output buffering and flushes the content after each API operation (starting/ending element blocks or writes). A new method ``xf.flush()`` can alternatively be used to explicitly flush the output. * ``lxml.html.document_fromstring`` has a new option ``ensure_head_body=True`` which will add an empty head and/or body element to the result document if missing. * ``lxml.html.iterlinks`` now returns links inside meta refresh tags. * New ``XMLParser`` option ``collect_ids=False`` to disable ID hash table creation. This can substantially speed up parsing of documents with many different IDs that are not used. * The parser uses per-document hash tables for XML IDs. This reduces the load of the global parser dict and speeds up parsing for documents with many different IDs. * ``ElementTree.getelementpath(element)`` returns a structural ElementPath expression for the given element, which can be used for lookups later. * ``xmlfile()`` accepts a new argument ``close=True`` to close file(-like) objects after writing to them. Before, ``xmlfile()`` only closed the file if it had opened it internally. * Allow "bytearray" type for ASCII text input. Other changes ------------- * LP#400588: decoding errors have become hard errors even in recovery mode. Previously, they could lead to an internal tree representation in a mixed encoding state, which lead to very late errors or even silently incorrect behaviour during tree traversal or serialisation. * Requires Python 2.6, 2.7, 3.2 or later. No longer supports Python 2.4, 2.5 and 3.1, use lxml 3.3.x for those. * Requires libxml2 2.7.0 or later and libxslt 1.1.23 or later, use lxml 3.3.x with older versions.

1 0

lxml 3.4.0 beta 1 released
by Stefan Behnel 10 Sep '14

10 Sep '14

Hi all, I just released the first beta version of the upcoming lxml 3.4. This is a feature release that mostly cleans up some prior deficiencies and speeds up parsing for documents that contain XML-IDs. Please give it some testing against your code. Note that this release drops support for older Python versions and now requires Py2.6/7 or Py3.2+. It also removes support for very old versions of libxml2 and libxslt (<=2008). The documentation is here: http://lxml.de/ Download: http://lxml.de/files/lxml-3.4.0beta1.tgz Signature: http://lxml.de/files/lxml-3.4.0beta1.tgz.asc Changelog: http://lxml.de/3.4/changes-3.4.0beta1.html Github: https://github.com/lxml/lxml/commit/638b9ce006ba32e46a09101e15c93ee94649a2ae This release was built using a pre-release version of Cython 0.21 (7a47dfdabcb9a9861480b1437f092c5f84911558). The final release is expected to use Cython 0.21 (but should build just fine with 0.20.x). If you are interested in commercial support or customisations for the lxml package, please contact me directly. Have fun, Stefan 3.4.0beta1 (2014-09-05) ======================= Features added -------------- * ``xmlfile(buffered=False)`` disables output buffering and flushes the content after each API operation (starting/ending element blocks or writes). A new method ``xf.flush()`` can alternatively be used to explicitly flush the output. * ``lxml.html.document_fromstring`` has a new option ``ensure_head_body=True`` which will add an empty head and/or body element to the result document if missing. * ``lxml.html.iterlinks`` now returns links inside meta refresh tags. * New ``XMLParser`` option ``collect_ids=False`` to disable ID hash table creation. This can substantially speed up parsing of documents with many different IDs that are not used. * The parser uses per-document hash tables for XML IDs. This reduces the load of the global parser dict and speeds up parsing for documents with many different IDs. * ``ElementTree.getelementpath(element)`` returns a structural ElementPath expression for the given element, which can be used for lookups later. * ``xmlfile()`` accepts a new argument ``close=True`` to close file(-like) objects after writing to them. Before, ``xmlfile()`` only closed the file if it had opened it internally. * Allow "bytearray" type for ASCII text input. Other changes ------------- * LP#400588: decoding errors have become hard errors even in recovery mode. Previously, they could lead to an internal tree representation in a mixed encoding state, which lead to very late errors or even silently incorrect behaviour during tree traversal or serialisation. * Requires Python 2.6, 2.7, 3.2 or later. No longer supports Python 2.4, 2.5 and 3.1, use lxml 3.3.x for those. * Requires libxml2 2.7.0 or later and libxslt 1.1.23 or later, use lxml 3.3.x with older versions.

2 1

Incremental Serialisation: Output buffering
by D.H.J. Takken 05 Sep '14

05 Sep '14

Hello, I am attempting to use etree.xmlfile to incrementally generate an XML stream into a file-like object, but I ran into a buffering problem. It looks like etree.xmlfile does not write straight into the supplied output, but is buffering internally. I searched for a way to force flushing the generated XML into the output, but did not find any. Looking at the source code, I see only one call to xmlOutputBufferFlush() and - as far as I can see - it is not called during incremental serialisation. Is my assumption about internal buffering correct? Is there a way to flush the internal buffer? Thanks a lot for helping me out!

2 4