Mailman 3 July 2006 - lxml - The Python XML Toolkit

Re: [lxml-dev] xml2 and xslt libraries
by Asif Iqbal 25 Jul '06

25 Jul '06

On 7/25/06, Asif Iqbal <vadud3(a)gmail.com> wrote: > > On 7/25/06, Stefan Behnel <behnel_ml(a)gkec.informatik.tu-darmstadt.de> > wrote: > > > > > Asif Iqbal wrote: > > > On 7/25/06, Stefan Behnel wrote: > > >> You can build etree statically, which completely avoids this kind > > >> of problems: > > >> > > >> http://codespeak.net/lxml/build.html#static-linking-on-windows > > > > > > I did see this since it comes with doc/build.txt file. Do I have to > > get > > > all the iconv and zlib all the other static libraries? > > > > No. It just means you have to build your flags by hand. I just happened > > to > > compile lxml statically today, against a Python 2.4 installed in my work > > directory. Apart from that, I only used libxml2 and libxslt for static > > compilation: > > > > cflags = [ > > "-I/path/to/libxml2-2.6.26/include", > > "-I/path/to/libxslt-1.1.17", > > "-I/path/to/PYTHON/include/python2.4", > > "-I/usr/include" > > ] > > xslt_libs = [ > > "-L/path/to/PYTHON/lib/python2.4", > > "/path/to/libxslt-1.1.17/libexslt/.libs/libexslt.a", > > "/path/to/libxslt-1.1.17/libxslt/.libs/libxslt.a", > > "/path/to/libxml2-2.6.26/.libs/libxml2.a", > > "-lz", "-lm", > > ] > > > > Worked for me, you'll likely have to adapt it. > > > I could not compile . I attached the compile output called > lxml.compile.out > Here is the attachment again lot smaller than last time. Hopefully it wont bounce this time BTW, in case you use 1.1alpha, its setup.py has a bug regarding the static > > setup. Feel free to apply this patch: > > > > Looks like 1.0.2 needed a patch to > > > --- setup.py.orig Tue Jul 25 08:03:15 2006 > +++ setup.py Tue Jul 25 08:03:29 2006 > @@ -18,7 +18,7 @@ > xslt_libs = [ > ] > result = (cflags, xslt_libs) > - # return result > + return result > raise NotImplementedError, \ > "Static build not configured, see doc/build.txt" > > > -- > Asif Iqbal > PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu > > > > -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu

1 0

[lxml-dev] missing ElementTree API?
by Martijn Faassen 25 Jul '06

25 Jul '06

Hi there, Reading the "What changed in Python 2.5" document I ran into the following bit of text concerning ElementTree: """ Comments and processing instructions are also represented as Element nodes. To check if a node is a comment or processing instructions: if elem.tag is ET.Comment: ... elif elem.tag is ET.ProcessingInstruction: ... """ As far as I can determine with a simple 'grep' on the source code, this isn't supported yet by lxml, at least the ProcessingInstruction bit. Since this now appears to be documented in a rather central document, perhaps we should. :) I'm a bit surprised about this use of ET.Comment - this would imply elem.tag returns the Comment class when its element is representing a comment? Regards, Martijn

2 6

Re: [lxml-dev] xml2 and xslt libraries
by Stefan Behnel 25 Jul '06

25 Jul '06

Asif Iqbal wrote: > On 7/25/06, Stefan Behnel wrote: >> You can build etree statically, which completely avoids this kind >> of problems: >> >> http://codespeak.net/lxml/build.html#static-linking-on-windows > > I did see this since it comes with doc/build.txt file. Do I have to get > all the iconv and zlib all the other static libraries? No. It just means you have to build your flags by hand. I just happened to compile lxml statically today, against a Python 2.4 installed in my work directory. Apart from that, I only used libxml2 and libxslt for static compilation: cflags = [ "-I/path/to/libxml2-2.6.26/include", "-I/path/to/libxslt-1.1.17", "-I/path/to/PYTHON/include/python2.4", "-I/usr/include" ] xslt_libs = [ "-L/path/to/PYTHON/lib/python2.4", "/path/to/libxslt-1.1.17/libexslt/.libs/libexslt.a", "/path/to/libxslt-1.1.17/libxslt/.libs/libxslt.a", "/path/to/libxml2-2.6.26/.libs/libxml2.a", "-lz", "-lm", ] Worked for me, you'll likely have to adapt it. BTW, in case you use 1.1alpha, its setup.py has a bug regarding the static setup. Feel free to apply this patch: -------------------------------------- Index: setup.py =================================================================== --- setup.py (Revision 30429) +++ setup.py (Arbeitskopie) @@ -109,6 +109,7 @@ # use the static setup as configured in setupStaticBuild sys.argv.remove('--static') cflags, xslt_libs = setupStaticBuild() + ext_args['extra_link_args'] = xslt_libs else: cflags = flags('xslt-config --cflags') xslt_libs = flags('xslt-config --libs') -------------------------------------- Stefan

1 0

[lxml-dev] xml2 and xslt libraries
by Asif Iqbal 25 Jul '06

25 Jul '06

Hi All How do I compile lxml with xml2 and xslt libraries from /usr/local/lib dir? I have two separate version of them. One is /usr/lib that comes with SUN and one in /usr/local/lib. I did run `python setup.py build_ext -L/usr/local/lib -R/usr/local/lib'. But only takes care of the -lxml. The xslt library was still being picked up from /usr/lib. The xslt library of SUN that sits on /usr/lib is integral part of SUN Sol 10 and used by SMF so I cannot get rid it. I need `xsltDocDefaultLoader' which is missing on /usr/lib/libxslt.so. Details: nm /usr/lib/libxslt.so | grep xsltDoc [431] | 116043| 297|FUNC |GLOB |0 |11 |xsltDocumentComp [495] | 133376| 3395|FUNC |GLOB |0 |11 |xsltDocumentElem [319] | 101736| 908|FUNC |GLOB |0 |11 |xsltDocumentFunction [156] | 101059| 677|FUNC |LOCL |0 |11 |xsltDocumentFunctionLoadDocument [277] | 48263| 127|FUNC |GLOB |0 |11 |xsltDocumentSortFunction nm /usr/local/lib/libxslt.so | grep xsltDoc [1251] | 254192| 4|OBJT |GLOB |0 |25 |xsltDocDefaultLoader [803] | 119356| 290|FUNC |LOCL |0 |10 |xsltDocDefaultLoaderFunc [1241] | 122376| 309|FUNC |GLOB |0 |10 |xsltDocumentComp [1527] | 139932| 3817|FUNC |GLOB |0 |10 |xsltDocumentElem [1601] | 105248| 1471|FUNC |GLOB |0 |10 |xsltDocumentFunction [1504] | 49964| 160|FUNC |GLOB |0 |10 |xsltDocumentSortFunction As you can see `xsltDocDefaultLoader' is only available on /usr/local/lib/libxslt.so -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu

2 1

Re: [lxml-dev] exceptions.TypeError: 'Argument must be string or unicode.'
by Stefan Behnel 24 Jul '06

24 Jul '06

Hi Olivier, Olivier Collioud wrote: > I'm using 1.0.2 installed with lxml-1.0.2.win32-static-py2.4.exe. > > I guess that I need to pick the source package before applying you > patch and then compile. Right. There are build instructions on the lxml page: http://codespeak.net/lxml/build.html#static-linking-on-windows > When do you think the next version will be provided ? 1.1 beta will be out early next month. As for 1.0.3: there are currently no critical bugs in 1.0.2, so I can't tell if it will be available any earlier - but not later either. Stefan

1 0

[lxml-dev] another iterparse segfault
by Andrew Lutomirski 22 Jul '06

22 Jul '06

This one mystifies me competely -- three line testcase attached. This crashes on lxml 1.1alpha static (python 2.4) on Windows as well as Python 2.4 on Gentoo with lxml trunk as of yesterday.

2 2

[lxml-dev] exceptions.TypeError: 'Argument must be string or unicode.'
by Olivier Collioud 21 Jul '06

21 Jul '06

Hello, I'm having this error: Exception exceptions.TypeError: 'Argument must be string or unicode.' in 'etree._setAttributeValue' ignored I suspect that I'm setting an attribute value to None but I don't know where. Is there a way to figure out where in my code the error occure ? Olivier. ------ World Intellectual Property Organization Disclaimer: This electronic message may contain privileged, confidential and copyright protected information. If you have received this e-mail by mistake, please immediately notify the sender and delete this e-mail and all its attachments. Please ensure all e-mail attachments are scanned for viruses prior to opening or using.

2 1

[lxml-dev] segfault in iterparse
by Andrew Lutomirski 19 Jul '06

19 Jul '06

Thanks for iterparse -- it (mostly) rocks. However, I can segfault it on large files when I try to clear out the tree to avoid unbounded memory use. See attached code. I'm _guessing_ that the problem is that iterparse doesn't like the deletion of the current node. Thanks, Andy

2 3

[lxml-dev] a C-level API for lxml
by Stefan Behnel 17 Jul '06

17 Jul '06

Hi all, as part of a project on lxml, I'm building an external element API module (objectify style) as a Pyrex extension. To make this independent of lxml itself, I decided to add an external C-level API that allows external modules to efficiently interface with the lxml module. Usage in other modules will be as easy as including a header file or cimporting a .pxd file in Pyrex, and then calling an init function from the external module. The match is done by comparing char* strings for the function names at initialisation time, so this is pretty future proof (no missing symbols when the C API changes etc.). This requires some changes in Pyrex, so lxml 1.1 will depend on a patched version (again), until (one day) my patches are accepted upstream. I also published some Python 2.5 related fixes, BTW, to make lxml 1.1 run nicely on Python 2.5. I can't currently test that since I can't get the 2.5 beta versions to work on my machine (broken compiled-in PYTHONPATH). Anyway, at least I got positive feedback that the exception stuff seems to be fixed. The Py_ssize_t fixes are not verified on 2.5, but should also work. A preliminary version of the patched Pyrex is here: http://codespeak.net/svn/lxml/pyrex/ So, if someone could test lxml with it under 2.5 (preferably on a 64-bit machine) ... When the lxml C-API is in place, it will be easy to add new functions to it (basically by adding the "public" keyword to a Pyrex C function). So I'd be glad if everyone who thinks this API would be useful for them could propose more functions to be made public. I know specifically that Andreas had a problem with extending the XPath implementation, so maybe there are ways to get this solved at the C level. This thread is the right place to discuss these things. Regards, Stefan

1 1

[lxml-dev] Python values in xpath functions
by Petr van Blokland 16 Jul '06

16 Jul '06

Stefan or others, Using XPath Python functions, right now I instantiate a global object that functions can work on. That works fine, however for multi-threading applications in the future that won't work. What do you thinks is the best approach: locking the lxml process while running an XSLT transformation or searching/finding (or waiting for) a way to pass Python variables through to XPath functions? Kind regards, Petr ---------------------------------------------- Petr van Blokland buro(a)petr.com | www.petr.com | +31 15 219 10 40 ----------------------------------------------

2 6