Mailman 3 June 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] lxml.objectify.deannotate refuses to clean nil nodes
by Robert Pierce 20 Jul '09

20 Jul '09

The nil node <Fubar/> is not deannotated as I would expect in the following snippet. I could not find a reference to this behaviour in the archives or documentation. Is this a design feature for which there is a work around, or a bug? I'm using lxml-2.2-py2.5-linux-i686. Thanks! #### CODE #### import lxml.etree import lxml.objectify x = lxml.objectify.fromstring('<root><Bar/></root>') x.Foo = '' x.Fubar = None lxml.objectify.deannotate(x) lxml.etree.cleanup_namespaces(x) print lxml.etree.tostring(x) #### END CODE ### <root><Bar/><Foo></Foo><Fubar xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/></root>

4 15

[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] lxml.html, now with ignored namespaces!
by Thomas Weigel 04 Jul '09

04 Jul '09

I am using lxml to parse HTML documents, which include a custom namespace (for example, "FRUIT"). In lxml 2.2.0, on Windows, this worked just fine, and elements could be processed based on this data. In lxml 2.2.2, on Linux, this fails. The above example becomes "FRUIT" as soon as it is parsed by lxml.html (or lxml.etree.HTMLParser()). I don't know if this is caused by the switch to Linux, or the upgrade to 2.2.2. I don't have control over the installation, so I can't switch to 2.2.2 under Windows, or 2.2.0 under Linux to check. I did find this reference (the only reference to this I could find) to the HTML ignoring namespaces: http://codespeak.net/lxml/lxmlhtml.html#running-html-doctests ...however, it wasn't doing that before, and it seems odd that this is only mentioned in the doctests section. Is there a way to work around this? Are custom namespaces simply not possible in lxml's HTML? Notes: 1. The XML parser will not work. Some documents will have legal HTML that breaks an XML parser, like " ". 2. Here is the sample code: ----- >>> import lxml.html as parser >>> document = parser.fromstring("""<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"><html xmlns="http://www.w3.org/TR/1999/REC-html-in-xml" xmlns:cs="http://something.com/cs" xml:lang="en" lang="en"><head><title>Help!</title></head><body>My namespaces are going to disappear!FRUIT</body></html>""") >>> print parser.tostring(document) ----- The output: ----- <html xmlns="http://www.w3.org/TR/1999/REC-html-in-xml" cs="http://something.com/cs" xml:lang="en" lang="en"><head><title>Help!</title></head><body>My namespaces are going to disappear!FRUIT</body></html> ----- Thomas Weigel

3 5

[lxml-dev] parsing DTDs - listing of valid elements
by Elliott Slaughter 01 Jul '09

01 Jul '09

Hi, I'm trying to get the elements in a DTD. Since these internals are not exported in the Python interface of lxml.etree, I am trying to write a Cython extension to do so, as previously suggested on this mailing list (see link below). http://codespeak.net/pipermail/lxml-dev/2009-January/004298.html To quote the message, "all you'd really need is the internal _c_dtd field of the DTD class, which you could cimport". I'm wondering exactly how I am supposed to do that (my attempts so far are described below). It would also be nice to know if the last attempt to do so was successful or not. Thanks. Any help would be appreciated. Here is what I've tried so far (on Python 2.5.4, Cython 0.11.2, Windows): The DTD class is not declared in etreepublic.pxd, so I can't just "cimport etreepublic". The actual DTD class definition is in dtd.pxi, as stated in the message. But I can't just "include 'dtd.pxi' " because it inherits from the _Validator class in lxml.etree.pyx . And I can't "cimport lxml.etree" because there is no file lxml.etree.pxd. I tried writing a lxml.etree.pxd file to circumvent these barriers (which was thoroughly confusing because _Validator contains an _ErrorLog which made me search through several other files...), but even when I got the entire thing to compile, it failed to load in Python: >>> import mydtd Traceback (most recent call last): File "<stdin>", line 1, in <module> File "lxml.etree.pxd", line 3, in mydtd (mydtd.c:513) cdef class _LogEntry: ValueError: lxml.etree._LogEntry does not appear to be the correct type object I have attached my lxml.etree.pxd in case I made any mistakes, in the event that this method can be made to work. -- Elliott Slaughter "Don't worry about what anybody else is going to do. The best way to predict the future is to invent it." - Alan Kay

2 3