Mailman 3 September 2008 - lxml - The Python XML Toolkit

[lxml-dev] lxml.html adds a default doctype to HTML documents
by James Graham 07 Sep '08

07 Sep '08

In [2]: from lxml import html In [3]: t = html.fromstring("<html><p>Hello World") In [4]: docinfo = t.getroottree().docinfo In [5]: docinfo.public_id Out[5]: '-//W3C//DTD HTML 4.0 Transitional//EN' Is it possible to prevent this from occurring? I couldn't see anything in the API documentation but I might have been missing something obvious. Silently gaining incorrect data is annoying :) -- "Eternity's a terrible thought. I mean, where's it all going to end?" -- Tom Stoppard, Rosencrantz and Guildenstern are Dead

1 0

[lxml-dev] lxml 2.1.2 and 2.0.9 released
by Stefan Behnel 05 Sep '08

05 Sep '08

Hi, lxml 2.1.2 and 2.0.9 are on PyPI. Both are bug-fix releases for the stable and mature release series. They mainly fix a thread-related memory problem that was introduced in the last releases of both branches. Updating is recommended. The complete changelog follows below. Have fun, Stefan 2.0.9 (2008-09-05) Bugs fixed * Memory problem when passing documents between threads. * Target parser did not honour the recover option and raised an exception instead of calling .close() on the target. 2.1.2 (2008-09-05) Features added * lxml.etree now tries to find the absolute path name of files when parsing from a file-like object. This helps custom resolvers when resolving relative URLs, as lixbml2 can prepend them with the path of the source document. Bugs fixed * Memory problem when passing documents between threads. * Target parser did not honour the recover option and raised an exception instead of calling .close() on the target.

1 0

[lxml-dev] [Fwd: [Bug 263898] [NEW] Windows Installer crashes due to access violation]
by Stefan Behnel 02 Sep '08

02 Sep '08

Hi, has anyone seem this before or could someone please test if this is reproducible on other machines? Thanks, Stefan -------------------------------------------------------------------------- Subject: [Bug 263898] [NEW] Windows Installer crashes due to access violation -------------------------------------------------------------------------- Public bug reported: I tried to install lxml-2.1.1.win32-py2.5.exe on my WinXP PC and got the attached crash from the installer. It happened after confirming all settings and clicking the "Next" button on the "Ready to install" page of the installer. Using Visual Studio Debugger to investigate crash : Callstack : ntdll.dll!_RtlEnterCriticalSection@4() + 0xb msvcr71.dll!_lock_file(void * pf=0x00000000) Line 236 C > msvcr71.dll!fprintf(_iobuf * str=0x00000000, const char * format=0x0012d278, ...) Line 63 + 0x6 C lxml-2.1.1.win32-py2.5.exe!00402ca8() user32.dll!77d48734() user32.dll!77d48bd9() user32.dll!77d541dc() user32.dll!77d541a9() user32.dll!77d53fd9() ntdll.dll!_RtlpFreeToHeapLookaside@8() + 0x26 ntdll.dll!_RtlFreeHeap@12() + 0x114 ntdll.dll!_RtlpFreeAtom@4() + 0x1b c5ffffff() Looking at the fprintf function I can see that "str" variable is NULL. _lock_file function using NULL pointer the access struture variable which eventually results in the reported crash. ** Affects: lxml Importance: Undecided Status: New -- Windows Installer crashes due to access violation https://bugs.launchpad.net/bugs/263898

1 0