lxml - The Python XML Toolkit May 2009

lxml@python.org

17 participants
23 discussions

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

11 Jan '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/>

4 4

[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] lxml has its page on launchpad
by Stefan Behnel 21 Sep '22

21 Sep '22

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

3 2

[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-dev] docinfo.doctype doesn't include internal entities?
by Sidnei da Silva 24 Jul '09

24 Jul '09

Hi there, I am looking for a way to output internal entities that have been parsed from the original document when writing out a tree, but apparently this is not exposed in any attribute. Here's an example: {{{ import lxml.etree document = """<?xml version="1.0"?> <!DOCTYPE application [ <!ENTITY nbsp "\ "> ]> <application> </application> """ tree = lxml.etree.fromstring(document) print tree.getroottree().docinfo.doctype }}} I would expect this to output: {{{ <!DOCTYPE application [ <!ENTITY nbsp "\ "> ]> }}} But instead it gives me: {{{ <!DOCTYPE application> }}} Is it a bug or I'm not looking at the right place? -- Sidnei da Silva

3 2

[lxml-dev] Compilation of lxml on Windows 64-bit
by Hanni Ali 17 Jul '09

17 Jul '09

Hi All, Came across this little gem of a Python module which seems able to translate some XML reports for me nicely. I was very pleased to see a Python 2.6 installer for windows, made checking it out much easier than many modules I use. So thanks for that. However although my testing seems to confirm this is the ideal module I do need to deploy to our production environment which is a 64-bit Windows environment running Python 2.6 (I code on 32-bit box for simplicity/resource reasons). Has anyone compiled and used lxml on this platform combination? If not does anyone foresee me having any issues compiling it for this platform? Thanks, Hanni

2 7

[lxml-dev] Binary egg for Mac OS X
by Alexander Limi 15 Jun '09

15 Jun '09

Hi, I'm working on documenting Deliverance / xdv for use with Plone. It has lxml as a dependency, and I have run into a serious issue: On Mac OS X, we can't assume that people have Xcode (ie. gcc and friends) installed, thus we can't really compile lxml on those computers, not even using the staticlxml[1] recipe. I see that there are binary eggs for Windows, is there a special reason why there are no binary eggs for OS X, or is it just a matter of not having the infrastructure to make it available? Happy to help find a solution if it's just a matter of locating a reliable way to get it compiled every time there is a new release. [1] http://pypi.python.org/pypi/z3c.recipe.staticlxml/ -- Alexander Limi · http://limi.net

6 11

[lxml-dev] Possible bug, libxml segfault?
by Avleen Vig 04 Jun '09

04 Jun '09

Hi folks :) I sent this message to the xml@gnome list, but that place is seems very quiet lately. I'm hoping someone here might have some insight. Indeed this might be a bug in lxml, we're not sure. Background: We use libxml and libxslt in one of our applications (specifically, in Python via lxml). Recently we've seen our application dying at strange times for no apparent reason. We managed to get a core file out of one crash, and the results of some of our debugging are here: http://xml.pastebin.com/m70c259d6 (I'd be happy to poke more in a particular direction on there, I'm a bit new to gdb :) To me, it seems the parser is complaining while trying to parse the namespaces in the <stylesheet> node in transforms/_base.xslt The node for that opens like this: <xsl:stylesheet version="1.0" xmlns="http://www.w3.org/1999/xhtml"; xmlns:xsl="http://www.w3.org/1999/XSL/Transform"; xmlns:tfxslt="http://tfnet.co.uk/ns/tfxslt"; xmlns:fb="http://www.facebook.com/2008/fbml"; extension-element-prefixes="tfxslt str exsl" exclude-result-prefixes="str exsl tfxslt fb" xmlns:error="http://www.woome.com/error/";> I dug a little deeper and found a bunch of the "address out of bounds" errors and thought I should ask here as I'm drawing a blank on where to go next. The problem happens intermittently, but usually several times a day. I could probably reproduce it. I also see the 'exclude-result-prefixes' mentioned in the backtrace, could that be involved here? Any suggestions you have would be much appreciated!

2 3

[lxml-dev] XML Documents & I18N (the way Cocoon does it)
by Alexis Georges 01 Jun '09

01 Jun '09

Hello everyone, I am maintaining a multilingual website which works with XML, XSLT to generate XHTML. I am working with Apache Cocoon (http://cocoon.apache.org/2.1/) using (among other things) their I18NTransformer. Basically I can use elements in the I18N (http://apache.org/cocoon/i18n/2.1) namespace, and then tell Cocoon to apply the I18NTransfomer to the document; this replaces the I18N elements with a localized value (eg. a formatted date/number, a translated label/attribute, etc...). I have been looking at lxml a little bit to see if I could move to a Python-based framework for the website. I am not quite sure how to go about the I18N part though. Using the Babel library (http://babel.edgewall.org/) along with request headers to generate localized data, I have everything I need. What is missing is the "parser" for the I18N elements. All I can think of right now is to implement a SAX parser, the way Cocoon does (in Java). Does anyone have suggestions? Am I making this too complicated? Thanks! Alexis

2 2

Re: [lxml-dev] problem about lxml encoding
by Stefan Behnel 31 May '09

31 May '09

Hi, please keep the list involved. Thanks. qhlonline wrote: > Since I am processing Chinese Webs. There are instances that some Webs > are not regular. When it said <meta encoding="GB2312">, we can't decode > the HTML string with GB2312 decoder, we found that this content is > encoded with GBK or GB18030 in fact. But the lxml parser will process it > according to the meta declaration. I have read the source of libxml2, > there are no "encoding" string match "GB2312","GBK" or "GB18030", but > some other encodings like ENCODING_2022_JP which may be a super set of > GB2312 I just don't know where in libxml2 or in lxml the <meta> declared > GB2312 encoding is converted to some other encodings that apparently > supported by libxml2's XML's xmlCharEncoding structure, and How? Most encodings are handled by libiconv. libxml2 only handles the 'normal' (or most common) XML encodings in its own code. > I think > since "GB18030" is a super set of "GB2312", if we change the lxml source > to let all <meta charset = 'GB2312'> strings were decoded with GB18030 > codec, then there will be no error even if the HTML file is not regular. No need to play with lxml's sources here. What should work is to read the HTML page into a byte string, decode it manually into a unicode string, and then let lxml parse that. That way, you also have full control over the decoding and can handle any decoding errors yourself. Stefan

2 1

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

lxml - The Python XML Toolkit May 2009