Mailman 3 October 2008 - lxml - The Python XML Toolkit

[lxml-dev] Building lxml 2.1.2 on windows
by Cserna, Zsolt (IT) 30 Oct '08

30 Oct '08

Hi all, I'm trying to build lxml 2.1.2 for python 2.5 on windows, but the linking fails with the following error: lxml.etree.obj : error LNK2019: unresolved external symbol _xsltProcessOneNode referenced in function ___pyx_pf_4lxml_5etree_13XSLTExtension_apply_templates I would like to link the libxml and the other libraries to lxml dynamically, not statically. Is it possible? It seems to me that xsltProcessOneNode is not defined in the windows version of libxslt (btw it's not defined in any .h files), however it's defined in unix .so files. I've installed all the dependencies, libxml version 2.6.31, libxslt 1.1.22, zlib 1.2, iconv 1.9, and using VC7.1 for building. Could you please advice on this? Any help/ideas would be appreciated. Thanks, Zsolt -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.

3 4

[lxml-dev] Simple doctypes not in docinfo.doctype
by F Wolff 27 Oct '08

27 Oct '08

Hallo list I've hit a snag with lxml and a DOCTYPE decleration. I don't know if I'm to blame here, but would appreciate help either way. I've tried this with an old (1.3.2) and newer (2.0.6) lxml version. (this example is roughly based on the code at http://codespeak.net/lxml/tutorial.html) from lxml import etree from StringIO import StringIO tree = etree.parse(StringIO("""<!DOCTYPE TS><TS></TS>""")) tree.docinfo.doctype '' >From my understanding this DOCTYPE declaration is valid (and occurring in the wild in Qt .ts files). My real issue is round-trip problems in a reading-writing cycle where the DOCTYPE is lost, but I guess not being able to use .docinfo.doctype is already a problem. Any help will be appreciated. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/vrot-mango

2 3

[lxml-dev] Lost DTD when serialising
by Alex Klizhentas 25 Oct '08

25 Oct '08

Hi All, I've read that " Serialising an ElementTree now includes any internal DTD subsets that are part of the document, as well as comments and PIs that are siblings of the root node. " (from changelog) but I've failed to achieve this goal, dtd data is lost: root = lxml.etree.parse(StringIO("""<?xml version="1.0" encoding="utf-8"?> <!DOCTYPE schema [ <!ATTLIST reference id ID #REQUIRED> <!ATTLIST joined_values id ID #REQUIRED> <!ATTLIST file id ID #REQUIRED> <!ATTLIST lookup id ID #REQUIRED> <!ATTLIST selector id ID #REQUIRED> <!ATTLIST Column id ID #REQUIRED> ]> <schema/> """)) print lxml.etree.tostring(root) prints me <schema/> What am I doing wrong? Thanks in advance, Alex

2 2

[lxml-dev] Handling namespaces in tags
by David Soulayrol 24 Oct '08

24 Oct '08

Hello, Is there some utility with lxml to retrieve the namespace and the name of a tag, or do we have to write on our own something like the following, anytime we need it ? ns, tag = node.tag[1:].find('}') -- David.

5 9

[lxml-dev] xmlHashComputeKey crash
by Kevin Watters 24 Oct '08

24 Oct '08

I've been getting crash reports from a user--the app is crashing when "import lxml.etree" happens. Unfortunately the default lxml build (for Windows, at least) doesn't include /Zi flags to build PDB files--so the stack doesn't include function names for the lxml bits. I'll be recompiling with /Zi, but still, I thought maybe I would ask here to see if anyone had run into this: 036ccbe0 01de0578 026a9128 10010ef8 05690ee0 libxml2!xmlHashComputeKey+0x12 036ccc04 01de0b3d 026a9128 10010ef8 05690ee0 libxml2!xmlHashUpdateEntry3+0xec 036ccc24 02bb2aee 026a9128 10010ef8 05690ee0 libxml2!xmlHashUpdateEntry2+0x19 036ccc40 0568c956 10010ef8 05690ee0 0568c6fb libxslt!xsltRegisterExtModuleFunction+0x54 036ccc54 0568cc30 03df5810 05629b42 00000000 libexslt!exsltCryptoRegister+0x45 036ccc5c 05629b42 00000000 03dd8b24 03dda424 libexslt!exsltRegisterAll+0xd WARNING: Stack unwind information not available. Following frames may be wrong. 036ccd08 1e0769ab 1e076210 03dd8b98 00000000 lxml_etree!initetree+0xdd22 036ccd1c 1e076276 03dda424 00b7f828 00000000 python25!_PyImport_LoadDynamicModule+0x7b 036ccd34 1e087247 00000000 03dd8b98 00b7f828 python25!imp_load_dynamic+0x66 036ccd4c 1e03aa81 00b7f828 03dd8b98 00000000 python25!PyCFunction_Call+0x47 036ccd7c 1e038b9b 036ccde0 00000000 03e07c40 python25!call_function+0x2b1 036ccdf8 1e03abd5 03e07c40 00000000 03dd62b0 python25!PyEval_EvalFrameEx+0x210b 036cce14 1e03aaf8 036ccea8 00000000 00000000 python25!fast_function+0x85 The xsltRegisterExtModuleFunction gets an xmlChar* "name" argument that appears to be a bad pointer, and is eventually accessed in xmlHashComputeKey.

2 3

[lxml-dev] HTML Meta Content-Type Tag not created as documenation states?
by John Krukoff 15 Oct '08

15 Oct '08

So, I was trying to figure out what happend to my meta tags when using the lxml.html module, and saw the note in the documentation that html.tostring will handle them as so: > Note: if include_meta_content_type is true this will create a > ``<meta http-equiv="Content-Type" ...>`` tag in the head; > regardless of the value of include_meta_content_type any existing > ``<meta http-equiv="Content-Type" ...>`` tag will be removed > However, that doesn't seem to actually be the case. It looks like etree.tostring is never creating the meta tag as html.tostring appears to expect, and instead the include_meta_content_type flag is simply controlling whether any found meta tag is removed from the output (with an re!). Python 2.5.2 (r252:60911, Sep 22 2008, 12:08:38) [GCC 4.1.2 (Gentoo 4.1.2 p1.1)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from lxml import html, etree >>> h = html.fromstring( '©2008' ) >>> html.tostring( h, encoding = 'us-ascii', include_meta_content_type = True ) '©2008' Not present there, so I figure maybe it's because it's not being treated as a complete document? >>> h = html.document_fromstring( '©2008' ) >>> html.tostring( h, encoding = 'us-ascii', include_meta_content_type = True ) '<html><body>©2008</body></html>' Parsing as document doesn't create it either. >>> html.tostring( h, encoding = 'iso-8859-1', include_meta_content_type = True ) '<html><body>\xa92008</body></html>' Okay, maybe it's because I'm using the default encoding for HTML (us-ascii)? Nope, trying something else doesn't cause it to exist either. >>> html.tostring( etree.ElementTree( h ), encoding = 'iso-8859-1', include_meta_content_type = True ) '<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">\n<html><body>\xa92008</body></html>' Maybe wrapping in an ElementTree? Get a doctype declaration out of that, but still no meta tag. >>> from lxml import etree >>> etree.__version__ u'2.1.2' In further testing, it appeared that if a Meta Content-Type tag was specified, it was passed though as is, as long as include_meta_content_type was True. The really weird part of this for me though, is that I've set include_meta_content_type on my much more complicated application server, and it does in fact appear to be generating meta tags automatically (or at least something in my XSLT heavy processing chain is). My testing was an attempt to duplicate that, and I was quite surprised when I couldn't. I've tried this on boxes with both libxml2 2.6.26 (RHEL5) & 2.6.32, and didn't see a difference there. -- John Krukoff <jkrukoff(a)ltgc.com> Land Title Guarantee Company

2 1

[lxml-dev] Use cssselect.py in Pyxer
by Dirk Holtwick 05 Oct '08

05 Oct '08

Hi, I wrote (yet another) templating language for Python based on Genshi, since Genshi itself does not yet work on Google App Engine (GAE). Since Genshi supports XPath I was thinking about using your cssselect.py module together with it. First tests showed that this seems to work fine. Now I would like to ship a little bit modified version of cssselect.py with this new templating language called "Pyxer" http://code.google.com/p/pyxer/ so the users do not have to install the whole lxml package (which does not work with GAE anyways I suppose). Since Python "lxml" is under the BSD license and Pyxer under MIT license I think this should not be such a big problem as long as I add your copyright notices to the file. Am I right? Thanks for your excellent work Dirk

2 2

[lxml-dev] Writing TargetParser in Cython
by Max Ivanov 02 Oct '08

02 Oct '08

Hi all! I'm trying to write TargetParser in Cython just to compare perfomance. The problem is with data types. If I define data method as "def data(self, char *data):" I'm unable to use it as TargetParser. I get " def data(self, char *data): UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-4: ordinal not in range(128)" error. I could instance and directly call data() and close() methods and everything works fine, but it refuses to work with lxml. Small testcase following: ----- _target.pyx ----------- cdef class Target: cdef list _data def __init__(self): self._data = [] def data(self, char *data): self._data.append(data) def close(self): return ''.join(self._data) ---- end of target.pyx ------ ---- test.py ------- # -*- encoding: utf-8 -*- import lxml.html from lxml import etree from _target import Target res = etree.HTML(u"ABCD", parser=lxml.html.HTMLParser(target = Target())) -------end of target.pyx ------

2 1

[lxml-dev] Warning: .stabs: description field '10543' too big, try a different debug format
by Terrence Brannon 01 Oct '08

01 Oct '08

Hello, I am using Cygwin and attempting to compile lxml. It worked under Cygwin on one laptop, so I dont know what is going on here --- both Cygwin distros are up to date. I am using Stackless Python if that makes a difference. Administrator@LIFEBOOK /usr/local/bin : $NAGARE_BIN/easy_install 'nagare[full]' Searching for nagare[full] Best match: nagare 0.1.0 Processing nagare-0.1.0-py2.5.egg nagare 0.1.0 is already the active version in easy-install.pth Installing nagare-admin script to /home/Administrator/prg/nagare-home/bin Using /home/Administrator/prg/nagare-home/lib/python2.5/site-packages/nagare-0.1.0-py2.5.egg Processing dependencies for nagare[full] Searching for lxml==2.1.1 Reading http://www.nagare.org/download/ Reading http://pypi.python.org/simple/lxml/ Reading http://codespeak.net/lxml Best match: lxml 2.1.1 Downloading http://codespeak.net/lxml/lxml-2.1.1.tgz Processing lxml-2.1.1.tgz Running lxml-2.1.1/setup.py -q bdist_egg --dist-dir /cygdrive/c/DOCUME~1/ADMINI~1/LOCALS~1/Temp/easy_install-yy5d-E/lxml-2.1.1/egg-dist-tmp-gaRX38 Building lxml version 2.1.1. NOTE: Trying to build without Cython, pre-generated 'src/lxml/lxml.etree.c' needs to be available. Using build configuration of libxslt 1.1.24 Building against libxml2/libxslt in the following directory: /usr/lib /cygdrive/c/DOCUME~1/ADMINI~1/LOCALS~1/Temp/ccULuerS.s: Assembler messages: /cygdrive/c/DOCUME~1/ADMINI~1/LOCALS~1/Temp/ccULuerS.s:22618: Warning: .stabs: description field '10543' too big, try a different debug format /cygdrive/c/DOCUME~1/ADMINI~1/LOCALS~1/Temp/ccULuerS.s:22619: Warning: .stabs: description field '10543' too big, try a different debug format /cygdrive/c/DOCUME~1/ADMINI~1/LOCALS~1/Temp/ccULuerS.s:22620: Warning: .stabs: description field '10543' too big, try a different debug format /cygdrive/c/DOCUME~1/ADMINI~1/LOCALS~1/Temp/ccULuerS.s:22621: Warning: .stabs: description field '10543' too big, try a different debug format

2 1