Mailman 3 April 2013 - lxml - The Python XML Toolkit

lxml 3.1.2 released
by Stefan Behnel April 12, 2013

April 12, 2013

Hi everyone, I just released lxml 3.1.2. This is a pure bug-fix release for the stable 3.1 series. You can get it from PyPI: http://pypi.python.org/pypi/lxml/3.1.2 The documentation is here: http://lxml.de/ Download: http://lxml.de/files/lxml-3.1.2.tgz Signature: http://lxml.de/files/lxml-3.1.2.tgz.asc Changelog: http://lxml.de/3.1/changes-3.1.2.html GitHub: https://github.com/lxml/lxml/commit/76c9042511bfee787efad2d2f5cbdb850c01fbd6 This release was built using Cython 0.18. 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.1.2 (2013-04-12) ================== Bugs fixed ---------- * LP#1136509: Passing attributes through the namespace-unaware API of the sax bridge (i.e. the ``handler.startElement()`` method) failed with a ``TypeError``. Patch by Mike Bayer. * LP#1123074: Fix serialisation error in XSLT output when converting the result tree to a Unicode string. * GH#105: Replace illegal usage of ``xmlBufLength()`` in libxml2 2.9.0 by properly exported API function ``xmlBufUse()``.

1 0

Bugathon on April 27th in München
by Stefan Behnel April 12, 2013

April 12, 2013

Hi all, the official date for the bugathon is Saturday, April 27th, starting at 10 AM It's taking place in München, Oettingenstraße 67. That's the usual meeting place of the local Python User Group. There were 8 signups so far, which I think is a reasonable size for this event. Since there was only one request for participation through IRC, I think it's best to drop the IRC participation completely as it would just add overhead to the otherwise local communication. NOTE: For those who signed up but haven't sent me an e-mail yet: please send me a private (i.e. direct, off-list) reply to this e-mail so that I have your e-mail address for the further planning. Stefan

1 0

performance decrease over 10000 rows with lpod(uses lxml) (open office library for python)
by yiğit bul April 5, 2013

April 5, 2013

Hey everyone , i am using lpod pytohn library to manipulate (just read for now actually) .ods files. lpod is using lxml behind. We have a problem with reading files that have so many rows , but it looks like an exponential bottleneck. I tracked the code down in the lpod library and reached where theres a xpath query running to get all the rows. xpath("table:table-row") operation (thats the exact operation): 10.000 rows , getting the whole rows is 0.1 seconds 12.000 rows , getting the whole rows is 0.5 seconds 15.000 rows , getting the whole rows is 1.3 seconds 20.000 rows , getting the whole rows is 7 seconds 30.000 rows , getting the whole rows is 20 seconds 60.000 rows , getting the whole rows is "i dont know how long" . is this usual ? --

2 1

anyone in for an lxml bugathon?
by Stefan Behnel April 5, 2013

April 5, 2013

Hi everyone, since the list of tickets in lxml's bug tracker just keeps ever growing, I'd like to organise a little bugathon to get rid of some of them and to at least look through the unprocessed ones and figure out if they are valid issues and what to do about them. https://bugs.launchpad.net/lxml There's lots of different tickets about various parts of lxml, reaching from opinions about unexpected behaviour over inappropriate APIs or missing features all the way to crashes and OS specific problems. Sometimes, it may just be the documentation that needs a little tweaking, sometimes it may turn out that only a week worth of programming would get something resolved. In a few cases, it's just unclear what the person reporting the issue was trying to say and if there really is a problem. Or it may be triggered by a bug in libxml2 or libxslt, in which case someone would need to forward the bug to the respective bug tracker and/or write an e-mail to their mailing list about it. So I'm sure there's something to do for everyone's level of experience, be it writing and/or minimising test cases, analysing and fixing actual bugs, updating the documentation or trying out provided test code and asking back for clarifications. Especially for those of you who have little experience with OSS development or who want to dive a bit deeper into their every day tool, this is an opportunity to learn something new and to help making lxml better. I'll see if I can get the local (München/DE) Python user group involved for this, but the whole thing would run through IRC anyway, so that everyone can participate. For those (if any) who participate locally, sponsorship for food and drinks would also be well appreciated. If there's sufficient interest for participation, I'll set up a Doodle to find a date that suites most people. It would most likely take place on one of the coming weekends, maybe during a Saturday (CEST). So, are there any volunteers that would like to participate in this? Stefan

5 6

How to pass xmlSaveOption flags to etree.tostring?
by Marcello Perathoner April 1, 2013

April 1, 2013

I need to serialize XHTML 1.1 without minimized empty elements. Specifically, I want to produce EPUB 2 files, which require XHTML 1.1, but some user agents, like epubreader for firefox, load the XHTML files from disk, whereas firefox uses the HTML parser and makes a big mess of minimized elements. So I wonder if there is a way to pass the option flags in libxml xmlSaveOption to etree.tostring (). In case there is no such way, I humbly request the feature to be added. Regards -- Marcello Perathoner webmaster(a)gutenberg.org

2 5