Mailman 3 November 2011 - lxml - The Python XML Toolkit

Pull request
by Henrik Zagerholm 18 Nov '11

18 Nov '11

Hello, I just wonder why this pull request has not been implemented? https://github.com/lxml/lxml/pull/18 Does it break anything else? Cheers, Henrik

1 0

Missing lxml-2.3.2 download file
by Liam Kirsher 13 Nov '11

13 Nov '11

Hi -- The download link on this page: http://lxml.de/index.html#download Is: http://lxml.de/files/lxml-2.3.2.tgz However that file is not found! I was able to download the file eventually from somewhere else, but that doesn't resolve the problem I'm having, which is that the buildout djangorecipe requires lxml-2.3.2, and tries to download it, and then fails. And I'm not sure how to bypass it. So I'm stuck. (Also, easy_install for lxml-2.3.2 fails for the same 404 reason.) If someone would just put that file at that address, it would be great! Liam

2 3

lxml 2.3.2 released
by Stefan Behnel 11 Nov '11

11 Nov '11

Hi everyone, I'm happy to announce the release of lxml 2.3.2. This is the second bug fix release of the stable 2.3 series. http://lxml.de/ http://pypi.python.org/pypi/lxml/2.3.2/ This release was built using Cython 0.15.1. It is recommended (although not required) to use at least libxml2 2.7.8 with lxml, which fixes a number of important bugs compared to the previous 2.7.x releases. Note that this release no longer supports CPython 2.3, which has long terminated its extended security-fix-only maintenance period back in March 2008. CPython 2.4.x and 2.5.x, although equally out of maintenance by python.org, continue to be supported due to their long term maintenance in certain Linux/Unix server installations. If you are interested in trainings, commercial support or customisations regarding the lxml package, please contact me directly. Have fun, Stefan 2.3.2 (2011-11-11) Features added * lxml.objectify.deannotate() has a new boolean option cleanup_namespaces to remove the objectify namespace declarations (and generally clean up the namespace declarations) after removing the type annotations. * lxml.objectify gained its own SubElement() function as a copy of etree.SubElement to avoid an otherwise redundant import of lxml.etree on the user side. Bugs fixed * Fixed the "descendant" bug in cssselect a second time (after a first fix in lxml 2.3.1). The previous change resulted in a serious performance regression for the XPath based evaluation of the translated expression. Note that this breaks the usage of some of the generated XPath expressions as XSLT location paths that previously worked in 2.3.1. * Fixed parsing of some selectors in cssselect. Whitespace after combinators ">", "+" and "~" is now correctly ignored. Previously it was parsed as a descendant combinator. For example, "div> .foo" was parsed the same as "div>* .foo" instead of "div>.foo". Patch by Simon Sapin.

1 0

lxml.etree.XMLSyntaxError: Extra content at the end of the document
by Thaman chand 11 Nov '11

11 Nov '11

Hi dev, I have a problem which I couldn't figure out after through quest. I have been trying to figure out the constantly the same error in my xml parser. I have following configuration and dealing with file(200MB-4GB) size: - Python 2.7 - lxml 2.3.1 The problem I understand is there is mismatch in the XML Syntax (start and end). The file is too huge I can't look inside at particular line between * 751969:438466*. But I tried what a naive do using sed command (sed -n 751969p filename) for specific line. So here are specific line output * 751969* <http://pastebin.com/nkBxnxZS> and *438466*<http://pastebin.com/NurZtPME>. It clearly shows that element start and end is not matching. But, the problem is I can't open such a huge file and do editing manually. Note: I have design the *validator* <http://pastebin.com/C9JnPz85>according to given schema and it shows the same problem. Question ------------ - **So how can I get rid off from such a error while parsing in future?** - **Or get get rid off from such an element which is not mandatory in parser?** Error goes here C:\Documents and Settings\****\Desktop>python example.py (751969, 438466) None file:///D:/files/average.mzML:751969:438466:FATAL:PARSER:ERR_DOCUMENT_END: Extra content at the end of the document Traceback (most recent call last): File "MainPaser.py", line 330, in <module> main() File "MainPaser.py", line 322, in main fast_iter(context, process_element) File "MainPaser.py", line 24, in fast_iter for event, elem in context: File "iterparse.pxi", line 478, in lxml.etree.iterparse.__next__ (src/lxml\lxml.etree.c:98432) File "iterparse.pxi", line 530, in lxml.etree.iterparse._read_more_events (src/lxml\lxml.etree.c:98953) File "parser.pxi", line 590, in lxml.etree._raiseParseError (src/lxml\lxml.etree.c:74696) lxml.etree.XMLSyntaxError: Extra content at the end of the document, line 751969, column 438466 Help me!! I posted same question in a *stack overflow*<http://stackoverflow.com/questions/8082456/lxml-etree-xmlsyantaxerror>

4 5

Trying to validate XML with an external DTD file.
by Matt Young 08 Nov '11

08 Nov '11

Hello everyone. I am trying to validate some xml with the lxml python library, and a file containing DTD. I am getting the following error: default.xml:4:0:ERROR:VALID:DTD_UNKNOWN_ELEM: No declaration for element contests. My xml file is here: http://pastie.org/2832639 and my DTD file is here: http://pastie.org/2832658 are there any obvious issues in my XML or DTD that would cause lxml to generate this error? -- -Matthew

1 1

Incorrect XPath translation of some CSS selectors
by Simon Sapin 04 Nov '11

04 Nov '11

Hi, Please consider the following session: >>> import lxml.cssselect >>> lxml.cssselect.css_to_xpath('a >#b') u"descendant-or-self::a/*[@id = 'b']" >>> lxml.cssselect.css_to_xpath('a >* #b') u"descendant-or-self::a/*//*[@id = 'b']" >>> lxml.cssselect.css_to_xpath('a > #b') u"descendant-or-self::a/*//*[@id = 'b']" The first and second translations are correct, but the third is not. The third CSS selector is equivalent to the first, not the second as the cssselect parser seems to think. The same bug happens with a class instead of an ID, and maybe in other cases. I can adapt the existing test suite so that is fails where it should not, if it helps. PS: should bug discussion go here on the mailing list or on Github’s or Launchpad’s bug-tracker? Regards, -- Simon Sapin

2 3

lxml.cssselect much slower on 2.3.1
by Simon Sapin 04 Nov '11

04 Nov '11

Hi, Thanks to everyone working on lxml. It helped a lot in developing WeasyPrint (http://weasyprint.org) lxml 2.3.1 changes how the descendant selector is implemented in cssselect: https://github.com/lxml/lxml/commit/503d276c79bbe74db7d210814cfd28132fbe2c9… This changes makes matching affected selectors much slower on big documents. On my machine, the following test gives 0.15 seconds with 2.3 but 45 seconds with 2.3.1: import time from lxml import html, cssselect document = html.parse('http://www.w3.org/TR/html5/Overview.html') match = cssselect.CSSSelector('dl dt') t1 = time.time() match(document) t2 = time.time() print t2 - t1 (You may want to download the file and parse that if you want to run the test repeatedly. It’s 4.7 MB of HTML.) Matching all selectors founds in the document’s stylesheets (as WeasyPrint does to render it in PDF) takes about one minute in 2.3. I don’t know about 2.3.1 because I gave up and killed it after one hour. Admittedly this document is bigger than most web pages (99k elements), but this problem also affects performance on smaller documents, though not as dramatically. By reading the changelog I don’t understand why the change was made or what effects it has (other than performance). When is A//B different or preffered to A/descendant::B ? Is the underlying performance problem fixable while keeping A//B? Best regards, -- Simon Sapin

2 9