Mailman 3 January 2009 - lxml - The Python XML Toolkit

[lxml-dev] cython version
by jholg＠gmx.de 07 Jan '09

07 Jan '09

Hi, Should this be updated to read Cython 0.10.3 now? http://codespeak.net/lxml/build.html: " easy_install Cython==0.9.8 lxml currently requires Cython 0.9.8, later versions were not tested. ... " Holger -- Sensationsangebot verlängert: GMX FreeDSL - Telefonanschluss + DSL für nur 16,37 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K1308T4569a

2 1

[lxml-dev] lxml 2.1.4/2.2beta1 Solaris 9 segv in test-suite
by Volker Paulsen 07 Jan '09

07 Jan '09

Hi, I just compiled lxml-2.1.4 (and lxml-2.2beta) with gcc 4.2.4 against - libxml2-2.7.2 - libxslt-1.1.24 Unfortunately the test "test_schematron_invalid_schema_empty" causes a segmentation violation with Python 2.5 and Python 2.6; Please find a gdb backtrace for Python 2.6 and lxml-2.1.4 (and lxml-2.2beta) attached. Regards, Volker Paulsen -- OrbiTeam Software GmbH & Co. KG http://www.orbiteam.de/ () Ascii Ribbon Campaign /\ Support plain text e-mail

3 6

[lxml-dev] lxml 2.1.5 released
by Stefan Behnel 06 Jan '09

06 Jan '09

Hi, I just released lxml 2.1.5 to PyPI. It's a minor bug fix release for the mature 2.1 series. This release was generated with Cython 0.10.3. Stefan 2.1.5 (2009-01-06) Bugs fixed * Potential memory leak on exception handling. This was due to a problem in Cython, not lxml itself. * Failing import on systems that have an io module.

2 3

[lxml-dev] whitespace in lxml.html vs. lxml.html.soupparser
by Ian Kallen 05 Jan '09

05 Jan '09

We're using CSSSelector to pull out document fragments. I noticed that the fragments from lxml.html.soupparser parses don't have extra whitespace (which is desirable) but fragments from lxml.html has extra whitespace cruft. For example w/soupparser: """<div class="post"><a name="8720086857907265707"/> <p/><div/>Josh Bancroft over at <a href="http://www.tinyscreenfuls.com/">TinyScreenfuls</a> puts together a great <a href="http://www.tinyscreenfuls.com/2008/01/site-statistics-i-care-about-as-a-blo…">roundup of stats</a> that matter to bloggers with Google Analytics screen shots and meaningful context. The comments are helpful too.<br/><br/>Highly recommended.<br/><br/>Technorati Tags: <a href="http://technorati.com/tag/stats" rel="tag">Stats</a>,<br/><a href="http://technorati.com/tag/bloggers" rel="tag">Bloggers</a>,<br/><a href="http://technorati.com/tag/blogging" rel="tag">Blogging</a><div/> </div>""" w/o soupparser: """<div class="post"><a name="8720086857907265707"/>  <p/><div/>Josh Bancroft over at <a href="http://www.tinyscreenfuls.com/">TinyScreenfuls</a> puts together a great <a href="http://www.tinyscreenfuls.com/2008/01/site-statistics-i-care-about-as-a-blo…">roundup of stats</a> that matter to bloggers with Google Analytics screen shots and meaningful context. The comments are helpful too.<br/><br/>Highly recommended.<br/><br/>Technorati Tags: <a href="http://technorati.com/tag/stats" rel="tag">Stats</a>,<br/><a href="http://technorati.com/tag/bloggers" rel="tag">Bloggers</a>,<br/><a href="http://technorati.com/tag/blogging" rel="tag">Blogging</a><div/> </div>       """ Is there a way to get the same output w/o soupparser as with? I'd hate to resort to post-processing the parses unnecessarily with regexps or such. thanks, -Ian

1 0

[lxml-dev] Working with <?xml-stylesheet ... ?>
by Martin Aspeli 05 Jan '09

05 Jan '09

Hi, I'd like to quickly/efficiently get a list of all <?xml-stylesheet ?> processing instructions in a given document. I have managed to find it via root_tree.getprevious(), but it seems I need to search through the siblings here to find the <?xml-stylesheet ?> if indeed there is one. I'm using the HTML parser. Is there a more natural API? Also, serialising using lxml.html.tostring() seems to lose the <?xml-stylesheet ?> PI. Is this by design? Cheers, Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book

2 3

[lxml-dev] lxml build problem, -arch ppc -arch i386
by Ian Bicking 03 Jan '09

03 Jan '09

Martin (copied) has been having a problem building Deliverance/lxml on a Mac using the latest static build stuff. Given the error messages (http://paste.plone.org/25648 for /usr/bin/python and http://paste.plone.org/25646 with macports Python), it seems like it might be related to the architecture. The compilation uses "-arch ppc -arch i386" pretty much unconditionally (in buildlibxml.py). Right now the Deliverance installation procedure is a bit opaque in this regard, so we couldn't really try just editing buildlibxml.py and rerunning. But I'm wondering why both -arch options are always there? Is the macports Python also a fat binary, or should it be contingent on which Python we're using? -- Ian Bicking : ianb(a)colorstudy.com : http://blog.ianbicking.org

3 2