Mailman 3 February 2008 - lxml - The Python XML Toolkit

[lxml-dev] Setting URL from lxml.html.fromstring, etc
by Ian Bicking 01 Mar '08

01 Mar '08

There doesn't seem to be any way to set a document's URL when parsing the document. E.g.: >>> from lxml import html >>> tree = html.parse('http://www.python.org') >>> tree.docinfo.URL 'http://www.python.org' But the parse function doesn't really take any arguments, and the URL attribute is write-only. Ideally you could do fromstring('...doc...', URL='location'). (Also I'm not sure why the URL shouldn't be writable.) Ian

2 11

[lxml-dev] PyUnicodeUCS2_Decode errors
by Ian Bicking 26 Feb '08

26 Feb '08

Lately we've been having problems with errors like "undefined symbol: PyUnicodeUCS2_Decode" when we do "import lxml.etree". When we build lxml from source the errors go away. I'm guessing this is because of systems that use UCS4 instead of UCS2, and lxml eggs that were compiled differently then the system. Is this the case? Is this a sign something is missing from the platform signature of egg files? Ian

3 3

[lxml-dev] Instantiated ObjectifiedElement
by Evan Grim 25 Feb '08

25 Feb '08

I've run into some curious behavior when trying to do something a bit non-standard with objectify. The code snippet below causes a hard crash. I know this isn't part of what is anticipated as normal use, but since it causes a crash I figure it's worth bringing up here to at least get some comments. <code> from lxml import etree, objectify class parent(objectify.ObjectifiedElement): pass p = parent() print p.tag </code> My use case here is that I'm trying to make a package that acts like objectify, but enforces schema restrictions. I'm trying my hand at writing custom classes that will do this, but maintain the nice interface that objectify provides. Where this fails is when I try to create an instance of one of my custom classes directly (as seen in the trivial code snippet above). I'm welcome to any suggestions, and at the very least wanted to bring the seg-fault producing condition to light so that the extension can be amended to prevent it.

2 4

[lxml-dev] lxml 2.0.1 released
by Stefan Behnel 24 Feb '08

24 Feb '08

Hi all, lxml 2.0.1 is out, changelog follows as usual. The most important changes may actually be the clean-up of the generated API documentation, including loads of added doc-strings all over the place. Have a look at it here: http://codespeak.net/lxml/api/index.html More documentation patches will definitely be appreciated! Have fun, Stefan 2.0.1 (2008-02-13) Features added * Child iteration in lxml.pyclasslookup. * Loads of new docstrings reflect the signature of functions and methods to make them visible in API docs and help() Bugs fixed * The module lxml.html.builder was duplicated as lxml.htmlbuilder * Form elements would return None for form.fields.keys() if there was an unnamed input field. Now unnamed input fields are completely ignored. * Setting an element slice in objectify could insert slice-overlapping elements at the wrong position. Other changes * The generated API documentation was cleaned up and disburdened from non-public classes etc. * The previously public module lxml.html.setmixin was renamed to lxml.html._setmixin as it is not an official part of lxml. If you want to use it, feel free to copy it over to your own source base. * Passing --with-xslt-config=/path/to/xslt-config to setup.py will override the xslt-config script that is used to determine the C compiler options.

3 15

[lxml-dev] Default prefixes for common XML namespaces *sometimes* doesn't work
by Christian Zagrodnick 23 Feb '08

23 Feb '08

Hi, in 2.0alpha5 the feature was added that there are defaults for some namespace prefixes (like xsi, xsd, py). Problem is, I sometimes still get things like <attribute xmlns:ns0="http://codespeak.net/lxml/objectify/pytype" ns0:pytype="str">bla</attribute> And I don't know why. What are the conditions when LXML uses (in this case) the py: prefix and when not? Or is it a bug? In the case above I used an ObjectPath with setattr. Regards, -- Christian Zagrodnick gocept gmbh & co. kg · forsterstrasse 29 · 06112 halle/saale www.gocept.com · fon. +49 345 12298894 · fax. +49 345 12298891

2 2

[lxml-dev] lxml 2.0.2 released
by Stefan Behnel 22 Feb '08

22 Feb '08

Hi all, lxml 2.0.2 is up on PyPI. This is a bug fix release for the stable 2.0 series. Changelog follows below. Have fun, Stefan 2.0.2 (2008-02-22) ================== Features added -------------- * Support passing ``base_url`` to file parser functions to override the filename of the file(-like) object. Bugs fixed ---------- * The prefix for objectify's pytype namespace was missing from the set of default prefixes. * Memory leak in Schematron (fixed only for libxml2 2.6.31+). * Error type names in RelaxNG were reported incorrectly. * Slice deletion bug fixed in objectify. Other changes ------------- * Enabled doctests for some Python modules (especially ``lxml.html``). * Add a ``method`` argument to ``lxml.html.tostring()`` (``method="xml"`` for XHTML output). * Make it clearer that methods like ``lxml.html.fromstring()`` take a ``base_url`` argument.

1 0

[lxml-dev] lxml namespaces
by Maxim Sloyko 20 Feb '08

20 Feb '08

Hi All! I have a little problem with XML namespaces. In my application I have two XML processors, that process the same document, one after the other. The first one looks for nodes in 'ns1' namespace, and substitutes them, according to some algorithm. After this processor is finished, it is guaranteed that there are no more 'ns1' nodes left in the tree. 'ns1' namespace dclaration is still there, in the root node (well, I put it there manually). Now, when this namespace is no longer needed, I want to get rid of it, because it confuses some other processors (namely, my browser) So, the question is, how do I do that? del tree.getroot().nsmap['ns1'] does not seem to do the trick :( Thanks in advance and Happy Holidays! -- Maxim Sloyko

3 5

[lxml-dev] Is resolve_entities not working ??
by Steve Howe 19 Feb '08

19 Feb '08

Hello all, Is the resolve_entities XmlParser constructor attribute not working or what did I do wrong ? howe@yezda ~ $ python Python 2.5.1 (r251:54863, Jan 9 2008, 05:34:21) [GCC 4.2.2 (Gentoo 4.2.2 p1.0)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from lxml import etree >>> print etree.__version__ 2.0.1 >>> print etree.LIBXML_VERSION (2, 6, 30) >>> import StringIO >>> xml = StringIO.StringIO('<?xml version="1.0" encoding="utf-8"?> <p>©</p>') >>> etree.parse(xml, etree.XMLParser(resolve_entities=False)) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "lxml.etree.pyx", line 2515, in lxml.etree.parse File "parser.pxi", line 1743, in lxml.etree._parseDocument File "parser.pxi", line 1775, in lxml.etree._parseMemoryDocument File "parser.pxi", line 1676, in lxml.etree._parseDoc File "parser.pxi", line 793, in lxml.etree._BaseParser._parseDoc File "parser.pxi", line 450, in lxml.etree._ParserContext._handleParseResultDoc File "parser.pxi", line 534, in lxml.etree._handleParseResult File "parser.pxi", line 476, in lxml.etree._raiseParseError lxml.etree.XMLSyntaxError: Entity 'copy' not defined, line 1, column 46 Thanks! -- Best Regards, Steve Howe

2 3

[lxml-dev] CPU you selected does not support x86-64 instruction set
by js 19 Feb '08

19 Feb '08

HI, I was trying to install lxml on FreeBSD 6.2 Xeon server with "easy_install lxml", but I got weird error "CPU you selected does not support x86-64 instruction set". I searched on the web with no luck. Does anybody know this error?

2 7

[lxml-dev] Explicit type checking and zope.security
by Christian Zagrodnick 18 Feb '08

18 Feb '08

Hi, lxml does quite some explicit type checking. For instance: object_path.addattr(root, value) gives me an error if root is security proxied: File "objectpath.pxi", line 74, in lxml.objectify.ObjectPath.addattr TypeError: Argument 'root' has incorrect type (expected lxml.etree._Element, got zope.security._proxy._Proxy) Is this explicit checking really necessary? It's quite annoying to have to unwrap everything (and eventually check manually for security) before putting it into lxml's hands. Any other ideas? Regards, -- Christian Zagrodnick gocept gmbh & co. kg · forsterstrasse 29 · 06112 halle/saale www.gocept.com · fon. +49 345 12298894 · fax. +49 345 12298891

2 2