Mailman 3 May 2013 - lxml - The Python XML Toolkit

[lxml-dev] lxml has its page on launchpad
by Stefan Behnel 11 Apr '23

11 Apr '23

Hi all, I added the lxml project to launchpad, the Ubuntu Bug-Tracker. It also has a FAQ engine and a couple of other goodies. https://launchpad.net/lxml It's easy to sign up for launchpad, BTW, no 90%-footnotes-contract. Have fun, Stefan

9 9

[lxml-dev] Checking whether a node is a comment/element
by Geoffrey Sneddon 10 Apr '23

10 Apr '23

Hi, What's the best way to check whether a given node is a comment or an element? For the former, I'm currently using isinstance(node, etree._Comment), which is rather obviously sub-optimal. -- Geoffrey Sneddon <http://gsnedders.com/>

6 6

[lxml-dev] Reparenting a node
by Lawrence Oluyede 30 Jan '23

30 Jan '23

I have a doc A and a doc B, I'd like to put a node extracted from A in the document B but I always get a ValueError: ValueError: Element is not a child of this node. I didn't find any "setparent" in the API. How can I do this? -- Lawrence, oluyede.org - neropercaso.it "It is difficult to get a man to understand something when his salary depends on not understanding it" - Upton Sinclair

3 2

[lxml-dev] lxml 2.0.5 released
by Stefan Behnel 11 Jan '23

11 Jan '23

Hi all, lxml 2.0.5 is on PyPI. This is a bug-fix-only release of the stable 2.0 series. Have fun, Stefan 2.0.5 (2008-05-01) Bugs fixed * Resolving to a filename in custom resolvers didn't work. * lxml did not honour libxslt's second error state "STOPPED", which let some XSLT errors pass silently. * Memory leak in Schematron with libxml2 >= 2.6.31.

3 4

[lxml-dev] Building LXML Trunk
by Sidnei da Silva 31 Aug '22

31 Aug '22

Hi, I've tried to build lxml from trunk today, on Win32. Got the following error: src\lxml\etree.c(880) : error C2059: syntax error : ')' src\lxml\etree.c(881) : error C2059: syntax error : ')' src\lxml\etree.c(882) : error C2059: syntax error : ')' src\lxml\etree.c(883) : error C2059: syntax error : ')' Any clue? Smells like a Pyrex issue? -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

4 4

lxml.objectify drops leading whitespace
by Wolfgang Schnerring 02 Oct '13

02 Oct '13

Hello, lxml.objectify drops leading whitespace before a tag: >>> lxml.etree.tostring(lxml.objectify.fromstring(' <a>foo</a>')) '<a>foo</a>' while lxml.etree handles the same situation just fine: >>> lxml.etree.tostring(lxml.etree.fromstring(' <a>foo</a>')) ' <a>foo</a>' What's the reason for the different behaviour? Is this intentional? Most importantly, how can I make lxml.objectify preserve whitespace correctly? Thanks for your help, Wolfgang

2 2

Changing encoding while parsing an HTML string
by Michael O'Leary 02 Jun '13

02 Jun '13

If I understand how the XML parser works, if it parses an XML string that begins with a header line like <?xml version="1.0" encoding="utf-8"?> it will parse the rest of the XML string using the encoding of the encoding it has found. So first of all, does the XML parser do this? If so, I'd like to know if something like this can be done, either automatically or manually, with the HTML parser. I have been parsing HTML strings that have been obtained from a random sampling of web sites, and I am wondering if there is a way to do something similar with these HTML strings. Typically, these HTML strings do not start with a header like, but most of them do have a meta tag of the form <meta charset="utf-8"> or <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" > I wouldn't expect that the HTML parser reads these tags and automatically sets the encoding to be used while parsing the rest of the HTML string (but I might as well ask: does it?). I could include code in my target's start tag handler that checks meta tags to see if they contain encoding information and calls the parser to set its encoding, but as far as I can see there isn't a way to set the encoding for an HTML parser after it has been created. That is, it looks like you can do this parser = etree.HTMLParser(target=my_target, encoding=my_encoding) but not this parser = etree.HTMLParser(target=my_target) .... figure out what value my_encoding should have .... parser.set_encoding(my_encoding) So I guess my underlying question is, how can I parse HTML strings and give the parser the best chance to use the right encoding for the part of the HTML string that is in the <body> .... </body> section of it? Thanks, Mike

2 1

Re: [lxml] wrong ELF class
by Wolfgang Buesser 27 May '13

27 May '13

>Le 27/05/2013 01:55, Wolfgang Buesser a écrit : >> I have installed python-lxml-2.3.4-6.1.1.x86_64.rpm >> >> […] >> >> Could it be possible, that the architecture in the RPM does not match >> 64-Bit (despite it's name)? >It depends, where did you get this RPM file? >> How can I check? >Try running this command: >file /usr/lib/python2.7/site-packages/lxml/etree.so >Cheers, >-- >Simon Sapin Hi Simon, Hi Holger, with your help I found out that the rpm was actually i586. I don't know how that happened. As far as I remember it was part of official SuSE release. Anyway I replaced with an rpm from rpm-find and now my application is running. Thanks Wolfgang

1 0

wrong ELF class
by Wolfgang Buesser 27 May '13

27 May '13

Hello, I am running SUSE 12.3 on an AMD-64 System. I have installed python-lxml-2.3.4-6.1.1.x86_64.rpm When lxml gets called from gnuradio-companion I get the following error-message: ImportError: /usr/lib/python2.7/site-packages/lxml/etree.so: wrong ELF class: ELFCLASS32 Could it be possible, that the architecture in the RPM does not match 64-Bit (despite it's name)? How can I check? How can I get a working python-lxml for my system? Thanks Wolfgang

3 2

Error seen when running unit tests
by Lindykid 25 May '13

25 May '13

Deal lxml Developers, I want to use your library for some projects that I will need XML parsing and XSD verification. I am attempting to install lxml 3.2.1 onto a RHEL 6.1 server which has python 2.6.6 installed. I did not use pip to build and install lxml, rather I used the 'python setup.py install'. Everything seemed to build and install fine. I was able to run through a few tutorials with out any issue. My problem came when I decided to try and run the unit tests that you have provided. I get one failure (see bottom of this E-Mail) when I run the 'make test' or 'python test.py -p -v' command. I have tried this on lxml versions of 3.1.2, 3.2.0, and 3.2.1 and I see the same test error on each release. I have attempted to sower the web, and the lxml mailing list archives to see if I could find any information on what is causing this test to fail, but I have come up empty. I am hoping that one of you can tell me what I am doing wrong, or what I can to to get this test to pass. Thanks so much for your time, - Chris # make test Skipping tests in lxml.cssselect - external cssselect package is not installed Comparing with ElementTree 1.2.6 TESTED VERSION: 3.2.1 Python: (2, 6, 6, 'final', 0) lxml.etree: (3, 2, 1, 0) libxml used: (2, 7, 6) libxml compiled: (2, 7, 6) libxslt used: (1, 1, 26) libxslt compiled: (1, 1, 26) 1479/1479 (100.0%): Doctest: xpathxslt.txt ====================================================================== ERROR: test_feed_parser_unicode (lxml.tests.test_elementtree.ETreeTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/lib64/python2.6/unittest.py", line 278, in run testMethod() File "/root/chris/lxml-3.2.1/src/lxml/tests/test_elementtree.py", line 3444, in test_feed_parser_unicode parser.feed(_str('<ro')) File "parser.pxi", line 1177, in lxml.etree._FeedParser.feed (src/lxml/lxml.etree.c:90354) File "parser.pxi", line 569, in lxml.etree._ParserContext._handleParseResult (src/lxml/lxml.etree.c:84648) File "parser.pxi", line 676, in lxml.etree._handleParseResult (src/lxml/lxml.etree.c:85816) File "parser.pxi", line 627, in lxml.etree._raiseParseError (src/lxml/lxml.etree.c:85308) XMLSyntaxError: None ---------------------------------------------------------------------- Ran 1479 tests in 14.117s FAILED (errors=1)

2 1