Mailman 3 April 2009 - lxml - The Python XML Toolkit

[lxml-dev] lxml has its page on launchpad
by Stefan Behnel 11 Apr '23

11 Apr '23

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

9 9

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

10 Apr '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/>

6 6

[lxml-dev] Reparenting a node
by Lawrence Oluyede 30 Jan '23

30 Jan '23

I have a doc A and a doc B, I'd like to put a node extracted from A in the document B but I always get a ValueError: ValueError: Element is not a child of this node. I didn't find any "setparent" in the API. How can I do this? -- Lawrence, oluyede.org - neropercaso.it "It is difficult to get a man to understand something when his salary depends on not understanding it" - Upton Sinclair

3 2

[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] 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] 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

[lxml-dev] xpath on text nodes
by Jamie Norrish 09 May '09

09 May '09

The xpath method is currently available only for ElementTree and Element objects. Is it possible for it to be available to text nodes also? My current use case is getting a certain length text context for a particular element node, and I'd like to implement that through a recursive call to a function that returns the content of a supplied text node appended to the content of the next text node in sequence (provided the required length has not been passed). Jamie

2 5

[lxml-dev] wsdl link validation.
by goldgod a 28 Apr '09

28 Apr '09

Hi, I am using the lxml. I have one wsdl(on the fly creation using soaplib). The wsdl contains three XSD schema.I am passing all XSD schema in one file as request. I want to validate the each XSD schema one by one. I need your help to implement this. I gone through the tutorial and found XSD schema validation can do but my wsdl contains XSD schema and wsdl messages also. Please advice me. -- Thanks & Regards, Goldgod

2 1

[lxml-dev] How to set an attribute with a xml-namepace
by Grimm, Markus 28 Apr '09

28 Apr '09

Hi all, I want to set a new element with an attribute using the xml-namespace, f.e. >> xml = "<root xml:space=\"preserve\"/>" >> root = etree.fromstring(xml) >> print etree.tostring(root) <root xml:space="preserve"/> everything fine, and now... >> root = etree.Element("root", space="preserve") >> print etree.tostring(root) <root space="preserve"/> How can I bind the space-attribute to the xml-namespace, so I can output the same result as above ? Thanks, Markus

3 3

[lxml-dev] eetree.fromsring() returns Element, expected ElementTree
by David Gardner 28 Apr '09

28 Apr '09

Ran into something that maybe a bug, or at least isn't clear from the documentation [http://codespeak.net/lxml/api/lxml.etree-module.html#fromstring] because it doesn't mention a return type for etree.fromstring(). I had expected it to behave similar to etree.parse(). Currently I have a work-around of: tree = etree.ElementTree(etree.fromstring(xml_data)) See below for simple test, and output. ------- #!/usr/bin/python import sys,StringIO from lxml import etree print "lxml.etree: ", etree.LXML_VERSION print "libxml used: ", etree.LIBXML_VERSION print "libxml compiled: ", etree.LIBXML_COMPILED_VERSION print "libxslt used: ", etree.LIBXSLT_VERSION print "libxslt compiled: ", etree.LIBXSLT_COMPILED_VERSION some_xml_data = "<root>data</root>" tree1=etree.fromstring(some_xml_data) tree2=etree.parse(StringIO.StringIO(some_xml_data)) print type(tree1) print type(tree2) -------------- lxml.etree: (2, 1, 5, 0) libxml used: (2, 7, 3) libxml compiled: (2, 6, 32) libxslt used: (1, 1, 24) libxslt compiled: (1, 1, 24) <type 'lxml.etree._Element'> <type 'lxml.etree._ElementTree'> 'lxml.etree._Element' object has no attribute 'write' -- David Gardner Pipeline Tools Programmer, "Sid the Science Kid" Jim Henson Creature Shop dgardner(a)creatureshop.com

2 2

[lxml-dev] Problem with XMLSchema and attribute_defaults
by Frank Millman 27 Apr '09

27 Apr '09

Hi all I need to validate an xml document with a schema, and at the same time populate it with any default attributes. This works correctly with minixsv, but it is rather slow, so I am trying lxml. It validates correctly, but I cannot get it to load the default attributes. This is what I am doing - schema = etree.XMLSchema(file='bpmnxpdl_31.xsd') parser = etree.XMLParser(schema=schema, attribute_defaults=True) root = etree.parse('order.xml', parser) Any assistance will be appreciated. Thanks Frank Millman

2 4

[lxml-dev] Forms, Cookies, Headers, and Time
by Akafubu Kibombo 23 Apr '09

23 Apr '09

I am trying to write a script which fetches a url, logs into the site, then fetches particular items from the page, and goes to the next page, fetching the same type of files on the new page until there are no new pages to fetch from. So I need form and cooke handling, as well as manipulating the headers. What do I need to use? I found this thread, but I don't understand it: http://codespeak.net/pipermail/lxml-dev/2008-December/004272.html. Also, I don't want to wipe out the server with so many requests, is there a "wait 2 - 3 seconds before fetching the next element" type function?.. Thank you so, so much. -A.F.

2 2

Re: [lxml-dev] lxml 2.2 released
by Stefan Behnel 17 Apr '09

17 Apr '09

jasonrbriggs(a)gmail.com wrote: > Hope you don't mind a quick question -- is "from the source > distribution" the only way to install on Python 3? There are currently no binary packages (that I know of) for Py3.0 or 3.1, so, yes, you have to build it yourself. Stefan

1 0

[lxml-dev] Porting lxml to QNX 6.4.0 issue
by Nelson Powell 14 Apr '09

14 Apr '09

I've attempted to port lxml to a QNX 6.4.0 PC (x86) and have already built and installed the libxslt, libxml2, and libgcrypt libraries wihtout any compile/link issues. The libraries were installed at /usr/local/lib which is part of my LD_LIBRARY_PATH. I'm using: libxslt 1.1.22 libxml2 2.7.2 libgcrypt 11.5.2 However, after building lxml, importing lxml produces the following messages in python: bash-3.2# python Python 2.5.2 (r252:60911, Oct 8 2008, 21:15:13) [GCC 4.2.4] on qnx6 Type "help", "copyright", "credits" or "license" for more information. >>> import lxml.etree as ET unknown symbol: gcry_cipher_open unknown symbol: gcry_cipher_ctl unknown symbol: gcry_md_hash_buffer unknown symbol: gcry_cipher_close unknown symbol: gcry_cipher_encrypt unknown symbol: gcry_check_version unknown symbol: gcry_cipher_decrypt unknown symbol: gcry_strerror Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: Unresolved symbols >>> Is there a way around this libgcrypt stuff? Anyone seen this before?

2 2

[lxml-dev] Unicode oddness
by Adam 08 Apr '09

08 Apr '09

The following seems wrong to me: I have a utf-8 encoded string with html containing the word 'Français': >>> html = '<html><head><title>Fran\xc3\xa7ais</title></head></html>' I feed it to lxml.html: >>> root = lxml.html.fromstring(html) When I get the text from lxml, it is a unicode string, but it has not been decoded!: >>> root.text_content() u'Fran\xc3\xa7ais' The expected output would be decoded unicode, i.e. the result of: >>> 'Fran\xc3\xa7ais'.decode('utf-8') u'Fran\xe7ais' Or just get back the encoded utf-8 string 'Fran\xc3\xa7ais' Either of these results would make sense and work for me. But the result is an odd confusion of the two. Is this an lxml problem, or have I misunderstood something? Thanks, Adam

2 2

[lxml-dev] Low ASCII values as text
by F Wolff 08 Apr '09

08 Apr '09

Hallo list I encountered a small issue from a user's error report, and a way to duplicate the issue is from this example code: from lxml import etree l = etree.Element('cow') l.text = unicode('\xd0\x94\x1bi\x1b\x1b\x1b?', "utf-8") etree.fromstring(etree.tostring(l)) With lxml 2.1 I get: XMLSyntaxError: PCDATA invalid Char value 27, line 1, column 13 It seems that etree.tostring() can generate XML that etree.fromstring() can't handle. But with a newer version (I think a beta of 2.2), I get "All strings must be XML compatible : Unicode or ASCII, no NULL bytes" on the assignment statement (l.text = ...). So in either case my question is if lxml's handling of these low values in ASCII is correct, since it doesn't seem possible to actually represent them at all, but I guess I am missing something important. As far as I know the XML 1.0 specification demands indicating these with numeric entities. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/monolingual-translation-fo…

2 1

[lxml-dev] XMLSchemaParseError if XML schema namespace uri is not "http://www.w3.org/2001/XMLSchema"
by Kev Dwyer 06 Apr '09

06 Apr '09

Hello, This is a re-post of my earlier posting, at Stefan's request, without the corporate boilerplate that I inadvertently sent last time. Sorry about that. Bug 354574 logged at Stefan's request. I have encountered a problem with schema object creation with lxml; the problem relates to namespace used for the root element of the schema. <snip> >>> import lxml.etree >>> et = lxml.etree.ElementTree(file=open('c:\\temp\\MySchema', 'r')) >>> et <lxml.etree._ElementTree object at 0x011B8AF8> >>> xsd = lxml.etree.XMLSchema(et) Traceback (most recent call last): File "<pyshell#4>", line 1, in <module> xsd = lxml.etree.XMLSchema(et) File "xmlschema.pxi", line 50, in lxml.etree.XMLSchema.__init__ (src/lxml/lxml.etree.c:120919) XMLSchemaParseError: Document is not XML Schema </snip> Looking in subversion (http://codespeak.net/svn/lxml/trunk/src/lxml/xmlschema.pxi), in the XMLSchema class I see: <snip> # work around for libxml2 bug if document is not XML schema at all #if _LIBXML_VERSION_INT < 20624: c_node = root_node._c_node c_href = _getNs(c_node) if c_href is NULL or \ cstd.strcmp(c_href, 'http://www.w3.org/2001/XMLSchema') != 0: raise XMLSchemaParseError, u"Document is not XML Schema" </snip> The schemas that I am using use this root element: <xsd:schema xmlns:xsd="http://www.w3.org/2000/10/XMLSchema"> If I change them to <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"> they validate. Can you explain why the earlier namespace definition is unacceptable? Is there a workaround? The schemas are not built by my application, so changing them might be an issue. Cheers, Kevin

2 2

[lxml-dev] setting xslt output encoding with lxml
by chris hoke 04 Apr '09

04 Apr '09

hi, (hope this is the right list for my question) To set the XSL output encoding I normally use <xsl:output encoding="..."/> in the stylesheet. At least in the Java based XSLT processors it is possible to set some attributes of xsl:output from the "outside" meaning when initializing or starting the transformation. So it is possible for example to overwrite any encoding specified in <xsl:output... with a different encoding. Is there any way to do this with LXML? The docs only have an example to set an XSLT parameter but not an XSLT processing configuration like the output encoding. BTW, the example on http://codespeak.net/lxml/xpathxslt.html#xslt >>> xslt_tree = etree.XML('''\ ... <xsl:stylesheet version="1.0" ... xmlns:xsl="http://www.w3.org/1999/XSL/Transform"<http://www.w3.org/1999/XSL/Transform>> ... <xsl:template match="/"> ... <foo><xsl:value-of select="$a" /></foo> ... </xsl:template> ... </xsl:stylesheet>''') >>> transform = etree.XSLT(xslt_tree) >>> f = StringIO('<a><b>Text</b></a>') >>> doc = etree.parse(f) seems to miss an <xsl:param name="a"/> parameter. I have not checked if it works without it but I guess it would be good style to declare any incoming parameters if not for setting a default value, would it not? thanks for any hints, Christof

3 3

[lxml-dev] problems with custom build
by Victor Borda 03 Apr '09

03 Apr '09

Hi List, I was very excited today to find the lxml module for python. As I need to write some xml checking scripts and finding bash scripting not well suited, I have decided to give python a try. So far I like it. However, here is the situation: 1) The target platform has an older RedHat installation with glibc2.3.4, so none of the binaries for libxml or libxslt were of any use. So I had to build from source on those. Not too painful. 2) However, trying to get lxml running has been really difficult. I need help here. 3) The target machine is not connected to the internet. It is not able to remotely retrieve packages. Questions/Steps: 0) There don't appear to be any rpm's for lxml. Is this correct? 1) Since I don't have an internet connection from this machine it means I have to build from source, don't I (ie easy_install is not an option)? 2) I have assumed that I do have to build from source so I have given it a shot. I copied over the lxml2.2 tar file, unzipped it. 3) I got setuptools-0.6c9-py2.3.egg and dropped in that unzipped directly, and ran python ez_setup.py which seemed to go fine. 4) Then I ran python setup.py build. The build seemed to go fine. 5) I go to run test.py and I get this error message: []# python test.py Traceback (most recent call last): File "test.py", line 595, in ? exitcode = main(sys.argv) File "test.py", line 558, in main test_cases = get_test_cases(test_files, cfg, tracer=tracer) File "test.py", line 260, in get_test_cases module = import_module(file, cfg, tracer=tracer) File "test.py", line 203, in import_module mod = __import__(modname) File "/home/victorborda/buildstuff/lxml-2.2/src/lxml/html/__init__.py", line 12, in ? from lxml import etree ImportError: /home/victorborda/buildstuff/lxml-2.2/src/lxml/etree.so: undefined symbol: xmlSchematronFree And with that, I tried running 'make test' and got the same result. The build appeared to go fine. The contents of lxml-2.2/build/lib.linux-x86_64-2.3/lxml are: -rw-r--r-- 1 root root 7637 Jun 19 2008 builder.py -rw-r--r-- 1 root root 28750 Nov 23 19:33 cssselect.py -rw-r--r-- 1 root root 18287 May 31 2008 doctestcompare.py -rw-r--r-- 1 root root 7641 Jul 9 2008 ElementInclude.py -rw-r--r-- 1 root root 6407 Feb 27 14:45 _elementpath.py -rwxr-xr-x 1 root root 3125362 Apr 3 04:49 etree.so drwxr-xr-x 2 root root 4096 Apr 3 04:49 html -rw-r--r-- 1 root root 21 Oct 22 2007 __init__.py -rwxr-xr-x 1 root root 846592 Apr 3 04:49 objectify.so -rw-r--r-- 1 root root 87 Mar 2 2008 pyclasslookup.py -rw-r--r-- 1 root root 8229 May 31 2008 sax.py -rw-r--r-- 1 root root 230 May 31 2008 usedoctest.py -- Best Regards, Victor Borda

2 1

[lxml-dev] XMLSchemaParseError: Document is not XML Schema
by Dwyer, Kevin 02 Apr '09

02 Apr '09

Hello, I have encountered a problem with schema object creation with lxml; the problem relates to namespace used for the root element of the schema. <snip> >>> import lxml.etree >>> et = lxml.etree.ElementTree(file=open('c:\\temp\\MySchema', 'r')) >>> et <lxml.etree._ElementTree object at 0x011B8AF8> >>> xsd = lxml.etree.XMLSchema(et) Traceback (most recent call last): File "<pyshell#4>", line 1, in <module> xsd = lxml.etree.XMLSchema(et) File "xmlschema.pxi", line 50, in lxml.etree.XMLSchema.__init__ (src/lxml/lxml.etree.c:120919) XMLSchemaParseError: Document is not XML Schema </snip> Looking in subversion (http://codespeak.net/svn/lxml/trunk/src/lxml/xmlschema.pxi), in the XMLSchema class I see: <snip> # work around for libxml2 bug if document is not XML schema at all #if _LIBXML_VERSION_INT < 20624: c_node = root_node._c_node c_href = _getNs(c_node) if c_href is NULL or \ cstd.strcmp(c_href, 'http://www.w3.org/2001/XMLSchema') != 0: raise XMLSchemaParseError, u"Document is not XML Schema" </snip> The schemas that I am using use this root element: <xsd:schema xmlns:xsd="http://www.w3.org/2000/10/XMLSchema"> If I change them to <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"> they validate. Can you explain why the earlier namespace definition is unacceptable? Is there a workaround? The schemas are not built by my application, so changing them might be an issue. Cheers, Kevin "Misys" is the trade name for Misys plc (registered in England and Wales). Registration Number: 01360027. Registered office: One Kingdom Street, London W2 6BL, United Kingdom. For a list of Misys group operating companies please go to http://www.misys.com/corp/About_Us/misys_operating_companies.html. This email and any attachments have been scanned for known viruses using multiple scanners. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. This email does not constitute the commencement of legal relations between you and Misys plc. Please refer to the executed contract between you and the relevant member of the Misys group for the identity of the contracting party with which you are dealing.

1 0