Mailman 3 September 2005 - lxml - The Python XML Toolkit

[lxml-dev] News on the dump() crash ?
by Steve Howe 09 Sep '05

09 Sep '05

Hello all, Any news on the dump() crash ? ###################################################### from lxml import etree as ElementTree ElementTree.dump(ElementTree.Element('a')) ###################################################### This is crashing Python 2.4.1 on XP. Could anyone please anyone confirm if this crashes interpreters on other platforms too ? -- Best regards, Steve mailto:howe@carcass.dhs.org

4 4

[lxml-dev] [PATCH] etree.fromstring and encoding
by Olivier Grisel 09 Sep '05

09 Sep '05

Hi list, I think ElementTree.fromstring expects a raw string as argument but the current lxml.etree.XML calls .encode("UTF-8") on it which is not nice if it's already an utf8 encoded string. Hence the patch. I'm not sure what should be expected though. If you guys have a clue :) I can write more tests with various encoded strings and unicode object as arg and try to compare ElementTree's behaviour with lxml's to better reproduce it in lxml. Just tell me if it's useful/required. Best, -- Olivier

2 1

[lxml-dev] lxml.etree.parse() fails with cStringIO objects
by dharana 04 Sep '05

04 Sep '05

--- >>> import StringIO >>> import cStringIO >>> import lxml.etree >>> lxml.etree.parse(StringIO.StringIO('<?xml version="1.0"?><foo></foo>')) <etree._ElementTree object at 0xb7e6b090> >>> lxml.etree.parse(cStringIO.StringIO('<?xml version="1.0"?><foo></foo>')) Traceback (most recent call last): File "<stdin>", line 1, in ? File "etree.pyx", line 993, in etree.parse --- I believe lxml should just check for a file-like object (I didn't looked at the code but it seems to be checking class types not interfaces). PD: Martijn, could you add a _version method to lxml? -- dharana

2 1