Mailman 3 October 2006 - lxml - The Python XML Toolkit

[lxml-dev] Cheese Shop link
by Ian Bicking Oct. 19, 2006

Oct. 19, 2006

Can you guys add some text like this to the Cheese Shop description: The in-development version of lxml can be found in the subversion repository at `http://codespeak.net/svn/lxml/trunk <http://codespeak.net/svn/lxml/trunk#egg=lxml-dev>`_ or installed with ``easy_install lxml==dev`` Thanks. -- Ian Bicking | ianb(a)colorstudy.com | http://blog.ianbicking.org

2 3

[lxml-dev] lxml and html encodings
by Chris Abraham Oct. 19, 2006

Oct. 19, 2006

Hello, We are getting some unexpected behavior when processing documents with a Shift_JIS encoding. We are trying to serialize an HTML document using an XSLT transform. Our results don't agree with the FAQ: http://codespeak.net/lxml/FAQ.html#why-can-t-lxml-parse-my-xml-from-unicode…. Please see the comments in the attached demo.py which reads in home.html and demonstrates our problem. Any ideas about this? Thanks. Chris

4 9

[lxml-dev] problem with lxml and copy.deepcopy
by Chris Abraham Oct. 17, 2006

Oct. 17, 2006

Hi, I'm having a problem with performing a copy.deepcopy on a list of elements. I'm finding the etree._Comment elements get turned into None. Please see my test case: >>> a = etree.HTML('<html><body><p>hi</p>  </body></html>') >>> b = a.xpath('//body/child::node()') >>> b [<Element p at 2b69f7d10d20>, ' ', , ' '] >>> import copy >>> c = copy.deepcopy(b) >>> c [<Element p at 2b69f7d1f7d0>, ' ', None, ' '] BTW, I'm using the CVS HEAD version of libxml2. Any ideas? Thanks, Chris

2 2

[lxml-dev] Building Problems
by Achim Kern Oct. 13, 2006

Oct. 13, 2006

Hello everybody, during googeling on how to write easier xml datastores with python I just found our project. Especialy the objectify modules impressed me. So to test things I wanted to install it. Unfortunatly I can not use the provided debian package as there is only one for version 1.03 not including the objectify extension. So I downloaded the source of 1.1.1 from codespeak.net extracted it and that's what it did. # tar -xzf lxml-1.1.1.tgz # ce lxml-1.1.1 # make clean test. python setup.py build_ext -i Building lxml version 1.1 running build_ext python test.py -p -v Traceback (most recent call last): File "test.py", line 591, in ? exitcode = main(sys.argv) File "test.py", line 554, in main test_cases = get_test_cases(test_files, cfg, tracer=tracer) File "test.py", line 254, in get_test_cases module = import_module(file, cfg, tracer=tracer) File "test.py", line 197, in import_module mod = __import__(modname) File "/tmp/lxml-1.1/src/lxml/tests/test_objectify.py", line 16, in ? from lxml import objectify ImportError: /tmp/lxml-1.1/src/lxml/objectify.so: undefined symbol: previousElement make: *** [test_inplace] Error 1 It builds just ok but when it comes to test it crashes. There seams to be something missing. I have installed libxml2 in version 2.6.26 and libxslt in version 1.1.17. I investigated the problem a little further with ldd and it gives me: # ldd -d src/lxml/objectify.so undefined symbol: PyTraceBack_Type (src/lxml/objectify.so) undefined symbol: _Py_NoneStruct (src/lxml/objectify.so) undefined symbol: PyString_Type (src/lxml/objectify.so) undefined symbol: previousElement (src/lxml/objectify.so) undefined symbol: PyExc_SystemError (src/lxml/objectify.so) undefined symbol: PyExc_ValueError (src/lxml/objectify.so) undefined symbol: PyExc_TypeError (src/lxml/objectify.so) undefined symbol: PyBaseString_Type (src/lxml/objectify.so) undefined symbol: PyExc_IndexError (src/lxml/objectify.so) undefined symbol: PyTuple_Type (src/lxml/objectify.so) undefined symbol: PyExc_AttributeError (src/lxml/objectify.so) undefined symbol: PyClass_Type (src/lxml/objectify.so) undefined symbol: nextElement (src/lxml/objectify.so) undefined symbol: PyList_Type (src/lxml/objectify.so) undefined symbol: PyExc_NotImplementedError (src/lxml/objectify.so) undefined symbol: PyBool_Type (src/lxml/objectify.so) undefined symbol: PyInstance_Type (src/lxml/objectify.so) undefined symbol: PyType_Type (src/lxml/objectify.so) undefined symbol: PyObject_GC_Del (src/lxml/objectify.so) undefined symbol: PyExc_NameError (src/lxml/objectify.so) linux-gate.so.1 => (0xffffe000) libexslt.so.0 => /usr/lib/libexslt.so.0 (0xa7eb2000) libxslt.so.1 => /usr/lib/libxslt.so.1 (0xa7e80000) libxml2.so.2 => /usr/lib/libxml2.so.2 (0xa7d67000) libpthread.so.0 => /lib/tls/libpthread.so.0 (0xa7d55000) libc.so.6 => /lib/tls/libc.so.6 (0xa7c23000) libgcrypt.so.11 => /usr/lib/libgcrypt.so.11 (0xa7bd2000) libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0xa7bcd000) libm.so.6 => /lib/tls/libm.so.6 (0xa7ba8000) libdl.so.2 => /lib/tls/libdl.so.2 (0xa7ba4000) libz.so.1 => /usr/lib/libz.so.1 (0xa7b90000) /lib/ld-linux.so.2 (0x75555000) libnsl.so.1 => /lib/tls/libnsl.so.1 (0xa7b7a000) Can anybody give me a hint where previousElement is defined? Or did I do something wrong? Thanks in advance. Achim Kern PS: if responding please put me into the cc, as I am currently not able to receive mails from mailinglists. Thank you.

4 13

[lxml-dev] 'dist' directory in Pyrex
by Sidnei da Silva Oct. 9, 2006

Oct. 9, 2006

Is it intentional that there's a 'dist' directory in the lxml copy of Pyrex? I suspect that it shouldn't be there (makes checkout needlesly long). -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

2 1

[lxml-dev] setup.py won't work with svn 1.4
by Sidnei da Silva Oct. 6, 2006

Oct. 6, 2006

Subversion 1.4 changed the .svn/entries format. setup.py will break. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

1 0

[lxml-dev] a buildout for lxml
by Martijn Faassen Oct. 5, 2006

Oct. 5, 2006

Hi there, I've just created what's called a "buildout" for lxml. Buildout is a new system for constructing Python applications and its constituent parts. More information can be found here: http://cheeseshop.python.org/pypi/zc.buildout/ Now before you read all that (it's fairly technical), let me explain what problem the lxml buildout tries to solve. Yesterday I tried using lxml's XMLSchema validator against an XML file and a schema. It gave a validation error, but to the best of my knowledge, the XML file should've been valid. Thinking it might perhaps be a bug that was fixed in more recent versions of libxml2, I set out to build and install libxml2 and libxslt locally, compiled lxml against it, and confirmed it: the document does validate against the schema with the most recent release of libxml2. Now downloading, building and installing libxml2 and libxslt and linking lxml against it is quite a bit of work. Buildout to the rescue! Now it's just this: $ svn co https://infrae.com/svn/buildout/lxml-recent/trunk lxml-recent $ cd lxml-recent $ python bootstrap/bootstrap.py $ bin/buildout and then wait. It'll download, configure and compile libxml2, libxslt, will downoad the lxml source and compile it against the libraries. In the end you end up with a script that invokes the Python interpreter with the right paths, so you can import the new lxml: $ bin/lxmlpython Though you can also manipulate the PYTHONPATH yourself in your scripts to put the lxml development egg on it, and then you can use the regular Python you used to run bootstrap.py with. To see how this works, you can take a look at buildout.cfg. This specifies how things are put together. Note that 'zc.recipe.cmmi' is a 'buildout recipe'. Recipes are components responsible for deployment of particular bits of an application. If zc.recipe.cmmi were released as an egg onto the cheeseshop, buildout would go out and download and install the recipe from there. Since it's not on the cheeseshop yet, I've installed it as a development-egg and included it as an svn:external, but this can be fixed by wrapping that into an egg. Many buildout recipes exist: this one does 'configure; make; make install', hence 'cmmi'. There are also recipes that build and install Zope 3, recipes to build tricky Python modules that don't work as an egg yet, and so on. New recipes can be developed. At Infrae's we've created recipes that can deploy OpenOffice in server mode, so that it can be used through UNO for document conversion purposes. This expanding pool of recipes will allow us to put together extremely complicated applications in a reproducable fashion. The idea of buildout is to have control - to know exactly what is installed and not to have to install everything into site-packages. buildout uses setuptools and easy_install internally, so the whole egg story just works; it expands on that. I think this way of building lxml has more benefits than just my single case. It'll allow one to deploy lxml against a known-good version of libxml2 and libxslt, at least on a linux system. It should also help testing and developing lxml - it becomes a lot more easy to test and develop against different versions of libxml2. I've placed this buildout in infrae.com SVN for now (checkout command above), but if people think this is interesting, I can integrate this into the lxml trunk. This can be done without harming the current way of working, but it'll allow someone to test against any version of libxml2 and libxslt a lot more easily than one can do now. Comments? Regards, Martijn

3 6

[lxml-dev] lxml replace() deletes tail
by Chris Abraham Oct. 2, 2006

Oct. 2, 2006

Hi, We have a question about the etree.replace() function. We found that it doesn't preserve the tail text from the replaced node when inserting a new node. Perhaps this is the intended behavior, but, to us, it was unexpected. In the example below, notice how the "tail" text is deleted when the <p> is replaced: >>> tree = etree.HTML("<html><body>text before<p>textin</p>tail</body></html>") >>> newel = etree.HTML("<html><body><div>new</div></body></html>") >>> tree[0].replace(tree[0][0], newel[0][0]) >>> etree.tostring(tree) '<html><body>text before<div>new</div></body></html>' Any ideas or comments? Thanks. Luke Tucker & Chris Abraham

2 1