Mailman 3 November 2006 - lxml - The Python XML Toolkit

[lxml-dev] pretty-printing
by Albert Brandl 24 Feb '07

24 Feb '07

Hi! I've posted a question about pretty-printing some time ago. Now I finally found the time to construct an example. The problem occurs with the following code: nsmap = dict (foo="http://foo.org", bar = "http://bar.org") e = Element("{http://foo.org}somefoo", nsmap = nsmap) s = Element("{http://bar.org}somebar", nsmap = nsmap) e.append(s1) et = ElementTree(e) et.write("foo.xml", pretty_print = True) This code creates the following XML file: <foo:somefoo xmlns:foo="http://foo.org" xmlns:bar="http://bar.org"> <bar:somebar xmlns:foo="http://foo.org" xmlns:bar="http://bar.org"/> </foo:somefoo> The problem is that "bar:somebar" redundantly declares the namespaces for "foo" and "bar", which affects both the readability and the size of the XML file. If the element "s" is appended to "e" by using the SubElement function instead of "append", the content of the XML file looks like I'd expect: <foo:somefoo xmlns:foo="http://foo.org" xmlns:bar="http://bar.org"> <bar:somebar/> </foo:somefoo> Is this a known bug? Thanks & best regards, Albert Brandl

4 5

[lxml-dev] XInclude does not support Resolvers?
by Sidnei da Silva 02 Dec '06

02 Dec '06

Hi there, I was looking at the XInclude functionality and noticed that it does use the 'resolvers'. Is that a missing feature or it just can't be done at all? -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

4 5

[lxml-dev] lxml 1.1 problems with python 2.3
by Martijn Faassen 01 Dec '06

01 Dec '06

Hi there, On Python 2.3 this segfaults with lxml 1.1 (it works with lxml 1.0): >>> from lxml import etree >>> etree.parse('sfadfdfd') On python 2.4 we get an error as we should (as the file sfafdfd doesn't exist). Additionally, the tests don't work anymore under Python 2.3. For lxml 1.1 some dependencies on Python 2.4's doctest module exist that don't work on Python 2.3, probably because we dropped the custom doctest that I added initially. For lxml 1.0 this is less bad, but there are still some dependencies on 'sorted()' and such in the tests. I don't think we actually ever explictly dropped support for Python 2.3. Perhaps we should for a particular version of lxml, but it'd be nice if we could track down this bug. It might indicate something wrong in Python 2.4 that just doesn't show up right away, I don't know. Regards, Martijn

4 14

[lxml-dev] setup.py issues
by Sidnei da Silva 29 Nov '06

29 Nov '06

Hi there, There are a couple regressions, and a feature request about the latest setup.py stuff: - Parsing the revision from svn 1.4 seems to have regressed. The attached patch replaces the code with a slightly modified version of the code in setuptools/commands/egg_info.py - Passing 'libraries' to 'Extension' needs to be made aware of '--static'. To be more precise, if --static is set, 'libraries' should have '<lib>_a' instead of '<lib>' (eg: 'xslt_a' instead of 'xslt'). - I would like to be able to pass 'static_include_dirs' and 'static_library_dirs' and 'static_cflags' as environment variables, which distutils already understands instead of changing setup.py. That would be 'INCLUDE' and 'LINK' environment variables on win32. -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

3 5

[lxml-dev] changes to lxml's setup.py
by Martijn Faassen 22 Nov '06

22 Nov '06

Hi there, I've just checked in a change to lxml that refactors lxml's setup.py to be more hackable. No functionality should've changed, though I'd like people to test the static build option on Windows. The way to set the static paths is somewhat easier now; see the static build section in doc/build.txt for more information. Basically I've split up a lot of stuff that'd grown into setup.py into separate modules and made everything a function instead of top-level code. This should make the code easier to follow and adjust in the future. Basically two new modules have been added: * versioninfo.py gets all kinds of version numbers and last change information * setupinfo.py prepares the building of Pyrex/C extensions. I've also made everything depend in a hard way on setuptools being available on the system - I think supporting old-style distutils is just going to be too much of a distraction to maintain properly. Next I'm investigating what to do with the --rpath option. I believe that currently --rpath is treated rather strangely by lxml's setup.py. --rpath normally expects a list of directory paths pointing to the libraries to link with. This is quite useful if you're linking against libraries in non-standard locations, such as in a buildout. It allows you to create a module that just works without having to set things like LD_LIBRARY_PATH before you try importing it. In case of lxml however, --rpath is ripped out of the list of options that reaches distutils/setuptools and action is taken by manipulating the other configuration parameters instead. This works so I haven't changed it (I hope), but it doesn't do enough. I *think* by adding an option --xslt-config pointing to a custom location for xslt-config we can make things work, though that would be hard to support in a straight buildout, as buildout obviously has no knowledge about passing such options. Food for more thought. Regards, Martijn

3 5

[lxml-dev] setup.py and buildout
by Martijn Faassen 22 Nov '06

22 Nov '06

Hi there, I reported previously that I created a buildout for lxml, but today I found out that is of limited utility: while it correctly links lxml against any libxml2 and libxslt library, it does still require the libxml and libxstl2 *headers* to be where xslt-config locates them, i.e. probably /usr/include I tried to hack up the setup.py so it would look elsewhere (it is supposed to respond to things like --include-dirs), but setup.py has grown to be rather complicated. This is a common problem with configuring from Python code - it grows all kinds of things which look useful but also make it very hard to expect some kind of uniform behavior across different systems configuring themselves this way. I hope that setup.py can still be adjusted so that buildout can be made to work. I *think* it's only not responding to --include-dirs that does it in. Regards, Martijn

5 8

[lxml-dev] lxml setup.py exslt link flag
by Luke Tucker 21 Nov '06

21 Nov '06

Hey, I came across a slight issue with the part of lxml's setup.py that adds a link flag for exslt when libxslt is installed in a directory with a name containing the string 'xslt'. not a huge deal, and probably a somewhat odd case, but I thought I'd mention it. If I understand correctly, to generate the link flag for libexslt, the result of 'xslt-config --libs' is taken and searched for an element containing 'xslt' and a new element is inserted which has 'exslt' instead. setup.py:117: ================================================= xslt_libs = flags('xslt-config --libs') # compile also against libexslt! for i, libname in enumerate(xslt_libs): if 'exslt' in libname: break if 'xslt' in libname: xslt_libs.insert(i, libname.replace('xslt', 'exslt')) break ================================================== In my case, I was working with an install of libxslt in: /home/ltucker/devel/deliverance.buildout/parts/libxslt and 'xslt-config --libs' returns: --------------------------------------------------------------------- -L/home/ltucker/devel/deliverance.buildout/parts/libxslt/lib -L/home/ltucker/devel/deliverance.buildout/parts/libxml2/lib -lxslt -lxml2 -lz -lm --------------------------------------------------------------------- in this case, the snippet above produces a list like --------------------------------------------------------------------- -L/home/ltucker/devel/deliverance.buildout/parts/libexslt/lib -L/home/ltucker/devel/deliverance.buildout/parts/libxslt/lib -L/home/ltucker/devel/deliverance.buildout/parts/libxml2/lib -lxslt -lxml2 -lz -lm --------------------------------------------------------------------- (adding a -L line rather than a -l) The final result was an etree.so that mysteriously didn't have a dependency on libexslt and produced run-time link errors. I believe this problem would apply to the lxml buildout as well, but it doesn't call the parts/libxslt/bin/xslt-config. (Do questions about the lxml buildout go to this list?) As a related side note, it might be nice to have the setup.py complain if 'xslt-config' can't be found. If it isn't around, it appears to silently create an etree.so with no dependencies on libxml2/xslt/exslt. - Luke

2 3

[lxml-dev] segfaults under python2.3 compiled with gcc 2.95.2
by Holger Joukl 20 Nov '06

20 Nov '06

Hi, -- long-post-warning -- I run into segfaults using a python2.3, gcc 2.95.2 - build (yes I know, mighty old compiler :-): Lib versions: lxml 1.1.2 libxml2-2.6.23 libxslt-1.1.15 Tests work fine with everything gcc3.4.4-built, using python2.4 (same lib versions), see below. Both segfaults seem to arise when an error is raised internally (though it is unclear why the first is an error - it does not raise an exception when run under python2.4/gcc3.4.4). 1. Using unprefixed namespace: python2.3 Python 2.3.4 (#6, Jul 20 2004, 11:09:38) [GCC 2.95.2 19991024 (release)] on sunos5 Type "help", "copyright", "credits" or "license" for more information. >>> from lxml import etree >>> elt = etree.fromstring("""<RvXML xmlns="myURI"></RvXML>""") Segmentation Fault (core dumped) backtrace: gdb /apps/prod/bin/python2.3 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "sparc-sun-solaris2.6"... (gdb) r -i -c 'from lxml import etree; elt = etree.fromstring("""<RvXML xmlns="myURI"></RvXML>""")' Starting program: /apps/prod/bin/python2.3 -i -c 'from lxml import etree; elt = etree.fromstring("""<RvXML xmlns="myURI"></RvXML>""")' [New LWP 2 ] [New LWP 3 ] [New LWP 4 ] [New LWP 5 ] Program received signal SIGSEGV, Segmentation fault. 0xff07b760 in pthread_mutex_lock () from /usr/lib/libthread.so.1 (gdb) bt #0 0xff07b760 in pthread_mutex_lock () from /usr/lib/libthread.so.1 #1 0xaa760 in PyThread_release_lock (lock=0x0) at Python/thread_pthread.h:532 #2 0x840c0 in PyEval_ReleaseThread (tstate=0x11abc0) at Python/ceval.c:339 #3 0xa4338 in PyGILState_Release (oldstate=PyGILState_UNLOCKED) at Python/pystate.c:473 #4 0xfe68ceb4 in __pyx_f_5etree__receiveError (__pyx_v_c_log_handler=0x2146c0, __pyx_v_error=0x206700) at src/lxml/etree.c:15789 #5 0xfe4324b4 in __xmlRaiseError (schannel=0xfe68ce68 <__pyx_f_5etree__receiveError>, channel=0xfe432880 <xmlParserWarning>, data=0x2146c0, ctx=0x206580, nod=0x0, domain=1, code=100, level=XML_ERR_WARNING, file=0x0, line=1, str1=0x25f01b "myURI", str2=0x0, str3=0x0, int1=0, col=13, msg=0xfe518560 "xmlns: URI %s is not absolute\n") at error.c:612 #6 0xfe43668c in xmlWarningMsg (ctxt=0xfe518560, error=XML_WAR_NS_URI_RELATIVE, msg=0xfe518560 "xmlns: URI %s is not absolute\n", str1=0x25f01b "myURI", str2=0x0) at parser.c:415 #7 0xfe44593c in xmlParseStartTag2 (ctxt=0x206580, pref=0xffbeee34, URI=0xffbeee30, tlen=0xffbeee2c) at parser.c:7854 #8 0xfe44719c in xmlParseElement (ctxt=0x206580) at parser.c:8437 #9 0xfe448b9c in xmlParseDocument (ctxt=0x206580) at parser.c:9129 #10 0xfe44e454 in xmlDoRead (ctxt=0x206580, URL=0x0, encoding=0x0, options=16386, reuse=1) at parser.c:13101 #11 0xfe44e80c in xmlCtxtReadMemory (ctxt=0x206580, buffer=0x24e568 "", size=29, URL=0x0, encoding=0x0, options=16386) at parser.c:13379 #12 0xfe649bd0 in __pyx_f_5etree_11_BaseParser__parseDoc (__pyx_v_self=0x1c8630, __pyx_v_c_text=0x14f8bc "<RvXML xmlns=\"myURI\"></RvXML>", __pyx_v_c_len=29, __pyx_v_c_filename=0x0) at src/lxml/etree.c:20945 #13 0xfe64d438 in __pyx_f_5etree__parseDoc (__pyx_v_text=0x14f8a8, __pyx_v_filename=0xf78f0, __pyx_v_parser=0x1c8630) at src/lxml/etree.c:22182 #14 0xfe64e5d4 in __pyx_f_5etree__parseMemoryDocument (__pyx_v_text=0x14f8a8, __pyx_v_url=0xf78f0, __pyx_v_parser=0x1c8630) at src/lxml/etree.c:22653 #15 0xfe62a39c in __pyx_f_5etree_XML (__pyx_self=0x1c8630, __pyx_args=0xf78f0, __pyx_kwds=0x0) at src/lxml/etree.c:9712 #16 0xcda64 in PyCFunction_Call (func=0x19a8f0, arg=0x2103f0, kw=0x0) at Objects/methodobject.c:77 #17 0x82238 in call_function (pp_stack=0xffbef2f8, oparg=2163696) at Python/ceval.c:3439 #18 0x7fd6c in eval_frame (f=0x1cd8f8) at Python/ceval.c:2116 #19 0x81318 in PyEval_EvalCodeEx (co=0x18db60, globals=0x0, locals=0x1cd8f8, args=0x0, argcount=0, kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0) at Python/ceval.c:2663 #20 0x8413c in PyEval_EvalCode (co=0x18db60, globals=0x1349c0, locals=0x1349c0) at Python/ceval.c:537 #21 0xa7164 in run_node (n=0x124158, filename=0x18db60 "", globals=0x1349c0, locals=0x1349c0, flags=0xffbef644) at Python/pythonrun.c:1267 #22 0xa7110 in run_err_node (n=0x124158, filename=0x18db60 "", globals=0x1349c0, locals=0x1349c0, flags=0xffbef644) at Python/pythonrun.c:1254 #23 0xa6ce0 in PyRun_StringFlags ( str=0x11a2d8 "from lxml import etree; elt = etree.fromstring(\"\"\"<RvXML xmlns=\"myURI\"></RvXML>\"\"\")\n", start=907888, globals=0x1349c0, locals=0x1349c0, flags=0xffbef644) at Python/pythonrun.c:1224 #24 0xa68cc in PyRun_SimpleStringFlags ( command=0x11a2d8 "from lxml import etree; elt = etree.fromstring(\"\"\"<RvXML xmlns=\"myURI\"></RvXML>\"\"\")\n", flags=0xffbef644) at Python/pythonrun.c:889 #25 0x1e034 in Py_Main (argc=4, argv=0xffbef72c) at Modules/main.c:399 #26 0x1d934 in main (argc=4, argv=0xffbef72c) at Modules/python.c:23 (gdb) Full backtrace: gdb /apps/prod/bin/python2.3 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "sparc-sun-solaris2.6"... (gdb) r -i -c 'from lxml import etree; elt = etree.fromstring("""<RvXML xmlns="myURI"></RvXML>""")' Starting program: /apps/prod/bin/python2.3 -i -c 'from lxml import etree; elt = etree.fromstring("""<RvXML xmlns="myURI"></RvXML>""")' [New LWP 2 ] [New LWP 3 ] [New LWP 4 ] [New LWP 5 ] Program received signal SIGSEGV, Segmentation fault. 0xff07b760 in pthread_mutex_lock () from /usr/lib/libthread.so.1 (gdb) help bt Print backtrace of all stack frames, or innermost COUNT frames. With a negative argument, print outermost -COUNT frames. Use of the 'full' qualifier also prints the values of the local variables. (gdb) bt full #0 0xff07b760 in pthread_mutex_lock () from /usr/lib/libthread.so.1 No symbol table info available. #1 0xaa760 in PyThread_release_lock (lock=0x0) at Python/thread_pthread.h:532 thelock = (pthread_lock *) 0x0 #2 0x840c0 in PyEval_ReleaseThread (tstate=0x11abc0) at Python/ceval.c:339 No locals. #3 0xa4338 in PyGILState_Release (oldstate=PyGILState_UNLOCKED) at Python/pystate.c:473 tcur = (PyThreadState *) 0x11abc0 #4 0xfe68ceb4 in __pyx_f_5etree__receiveError (__pyx_v_c_log_handler=0x2146c0, __pyx_v_error=0x206700) at src/lxml/etree.c:15789 __pyx_v_gil_state = PyGILState_UNLOCKED #5 0xfe4324b4 in __xmlRaiseError (schannel=0xfe68ce68 <__pyx_f_5etree__receiveError>, channel=0xfe432880 <xmlParserWarning>, data=0x2146c0, ctx=0x206580, nod=0x0, domain=1, code=100, level=XML_ERR_WARNING, file=0x0, line=1, str1=0x25f01b "myURI", str2=0x0, str3=0x0, int1=0, col=13, msg=0xfe518560 "xmlns: URI %s is not absolute\n") at error.c:612 file = 0x0 int1 = 2180800 msg = 0xfe518560 "xmlns: URI %s is not absolute\n" ctxt = 0x206580 node = 0x0 str = 0x209418 "xmlns: URI myURI is not absolute\n" input = 0x206700 to = 0x206700 baseptr = 0x0 #6 0xfe43668c in xmlWarningMsg (ctxt=0xfe518560, error=XML_WAR_NS_URI_RELATIVE, msg=0xfe518560 "xmlns: URI %s is not absolute\n", str1=0x25f01b "myURI", str2=0x0) at parser.c:415 schannel = 0 #7 0xfe44593c in xmlParseStartTag2 (ctxt=0x206580, pref=0xffbeee34, URI=0xffbeee30, tlen=0xffbeee2c) at parser.c:7854 URL = (xmlChar *) 0x25f01b "myURI" uri = 0x20c1a8 q = (xmlChar *) 0x25f01b "myURI" cons = 2146728 len = 5 alloc = 0 localname = (xmlChar *) 0x25f015 "RvXML" prefix = (xmlChar *) 0x0 attname = (xmlChar *) 0x25efea "xmlns" aprefix = (xmlChar *) 0x0 nsname = (xmlChar *) 0x1 <Address 0x1 out of bounds> attvalue = (xmlChar *) 0x260bde "myURI\"></RvXML>" atts = (xmlChar **) 0x0 maxatts = 0 nratts = 0 nbatts = 0 nbdef = 0 i = 2493392 j = 2146728 nbNs = 0 attval = 0 base = (xmlChar *) 0x260bd0 "<RvXML xmlns=\"myURI\"></RvXML>" cur = 1 ---Type <return> to continue, or q <return> to quit--- nsNr = 0 #8 0xfe44719c in xmlParseElement (ctxt=0x206580) at parser.c:8437 name = (xmlChar *) 0x0 prefix = (xmlChar *) 0xfe45f03c "@\003¹¶\221* \001\200¢ " URI = (xmlChar *) 0xffbeee68 "" node_info = { node = 0xffbeee70, begin_pos = 804524, begin_line = 4290704056, end_pos = 1196856, end_line = 1023380 } line = 1 tlen = 5 ret = 0x0 nsNr = 0 #9 0xfe448b9c in xmlParseDocument (ctxt=0x206580) at parser.c:9129 start = "<RvX" enc = 2123136 #10 0xfe44e454 in xmlDoRead (ctxt=0x206580, URL=0x0, encoding=0x0, options=16386, reuse=1) at parser.c:13101 ret = 0x0 #11 0xfe44e80c in xmlCtxtReadMemory (ctxt=0x206580, buffer=0x24e568 "", size=29, URL=0x0, encoding=0x0, options=16386) at parser.c:13379 input = 0x24e568 stream = 0x206580 #12 0xfe649bd0 in __pyx_f_5etree_11_BaseParser__parseDoc (__pyx_v_self=0x1c8630, __pyx_v_c_text=0x14f8bc "<RvXML xmlns=\"myURI\"></RvXML>", __pyx_v_c_len=29, __pyx_v_c_filename=0x0) at src/lxml/etree.c:20945 __pyx_v_state = (PyThreadState *) 0x11abc0 __pyx_v_result = (xmlDoc *) 0x14f8bc __pyx_v_pctxt = (xmlParserCtxt *) 0x206580 __pyx_r = (xmlDoc *) 0x0 __pyx_1 = 0 __pyx_2 = (PyObject *) 0x0 __pyx_3 = (PyObject *) 0x0 __pyx_4 = (xmlDoc *) 0x206580 __pyx_5 = (PyObject *) 0x0 __pyx_6 = (PyObject *) 0x206580 __pyx_7 = (PyObject *) 0x0 #13 0xfe64d438 in __pyx_f_5etree__parseDoc (__pyx_v_text=0x14f8a8, __pyx_v_filename=0xf78f0, __pyx_v_parser=0x1c8630) at src/lxml/etree.c:22182 __pyx_v_c_filename = 0x0 __pyx_v_filename_utf = (PyObject *) 0xf78f0 __pyx_r = (xmlDoc *) 0x14f8a8 __pyx_1 = 0 __pyx_2 = (PyObject *) 0x0 __pyx_4 = (xmlDoc *) 0x1c8630 __pyx_5 = (xmlDoc *) 0x1c8630 #14 0xfe64e5d4 in __pyx_f_5etree__parseMemoryDocument (__pyx_v_text=0x14f8a8, __pyx_v_url=0xf78f0, __pyx_v_parser=0x1c8630) at src/lxml/etree.c:22653 __pyx_r = (struct LxmlDocument * ?) 0x0 ---Type <return> to continue, or q <return> to quit--- __pyx_1 = 0 __pyx_2 = (PyObject *) 0x0 __pyx_3 = (xmlDoc *) 0x14f8a8 #15 0xfe62a39c in __pyx_f_5etree_XML (__pyx_self=0x1c8630, __pyx_args=0xf78f0, __pyx_kwds=0x0) at src/lxml/etree.c:9712 __pyx_v_text = (PyObject *) 0x14f8a8 __pyx_v_parser = (struct __pyx_obj_5etree__BaseParser * ?) 0x1c8630 __pyx_v_doc = (struct LxmlDocument * ?) 0xf78f0 __pyx_r = (PyObject *) 0x1c8630 __pyx_2 = (PyObject *) 0x1c8630 __pyx_argnames = {0xfe696848 "text", 0xfe695728 "parser", 0x0} #16 0xcda64 in PyCFunction_Call (func=0x19a8f0, arg=0x2103f0, kw=0x0) at Objects/methodobject.c:77 meth = 0xfe62a17c <__pyx_f_5etree_XML> self = (PyObject *) 0x0 size = 2163708 #17 0x82238 in call_function (pp_stack=0xffbef2f8, oparg=2163696) at Python/ceval.c:3439 callargs = (PyObject *) 0x2103f0 flags = 2163696 na = 2163696 nk = 0 n = 1 pfunc = (PyObject **) 0x1cda44 func = (PyObject *) 0x19a8f0 x = (PyObject *) 0xffbef2f8 w = (PyObject *) 0x2103f0 #18 0x7fd6c in eval_frame (f=0x1cd8f8) at Python/ceval.c:2116 stack_pointer = (PyObject **) 0x1cda48 next_instr = (unsigned char *) 0x14f97d "Z\003" opcode = 131 oparg = 1 why = WHY_NOT err = 0 x = (PyObject *) 0x14f8a8 v = (PyObject *) 0x19b0d0 w = (PyObject *) 0x19a660 u = (PyObject *) 0x197e90 t = (PyObject *) 0x83 stream = (PyObject *) 0x0 fastlocals = (PyObject **) 0x1cda44 freevars = (PyObject **) 0x1cda44 retval = (PyObject *) 0x0 tstate = (PyThreadState *) 0x11abc0 co = (PyCodeObject *) 0x18db60 instr_ub = -1 instr_lb = 0 first_instr = (unsigned char *) 0x14f964 "d" names = (PyObject *) 0x133930 consts = (PyObject *) 0x196a58 #19 0x81318 in PyEval_EvalCodeEx (co=0x18db60, globals=0x0, locals=0x1cd8f8, args=0x0, argcount=0, kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0) at Python/ceval.c:2663 ---Type <return> to continue, or q <return> to quit--- kwcount = 0 closure = (PyObject *) 0x14f97d f = (PyFrameObject *) 0x1cd8f8 retval = (PyObject *) 0x0 fastlocals = (PyObject **) 0x1cda44 freevars = (PyObject **) 0x1cda44 tstate = (PyThreadState *) 0x11abc0 x = (PyObject *) 0x0 u = (PyObject *) 0xffffffff #20 0x8413c in PyEval_EvalCode (co=0x18db60, globals=0x1349c0, locals=0x1349c0) at Python/ceval.c:537 No locals. #21 0xa7164 in run_node (n=0x124158, filename=0x18db60 "", globals=0x1349c0, locals=0x1349c0, flags=0xffbef644) at Python/pythonrun.c:1267 co = (PyCodeObject *) 0x18db60 v = (PyObject *) 0x124158 #22 0xa7110 in run_err_node (n=0x124158, filename=0x18db60 "", globals=0x1349c0, locals=0x1349c0, flags=0xffbef644) at Python/pythonrun.c:1254 No locals. #23 0xa6ce0 in PyRun_StringFlags ( str=0x11a2d8 "from lxml import etree; elt = etree.fromstring(\"\"\"<RvXML xmlns=\"myURI\"></RvXML>\"\"\")\n", start=907888, globals=0x1349c0, locals=0x1349c0, flags=0xffbef644) at Python/pythonrun.c:1224 No locals. #24 0xa68cc in PyRun_SimpleStringFlags ( command=0x11a2d8 "from lxml import etree; elt = etree.fromstring(\"\"\"<RvXML xmlns=\"myURI\"></RvXML>\"\"\")\n", flags=0xffbef644) at Python/pythonrun.c:889 m = (PyObject *) 0x11a2d8 d = (PyObject *) 0x11a2d8 v = (PyObject *) 0x101 #25 0x1e034 in Py_Main (argc=4, argv=0xffbef72c) at Modules/main.c:399 c = 1155800 sts = 1138696 command = 0x11a2d8 "from lxml import etree; elt = etree.fromstring(\"\"\"<RvXML xmlns=\"myURI\"></RvXML>\"\"\")\n" filename = 0x0 fp = (FILE *) 0x116008 p = 0x11a2d8 "from lxml import etree; elt = etree.fromstring(\"\"\"<RvXML xmlns=\"myURI\"></RvXML>\"\"\")\n" inspect = 1 unbuffered = 0 skipfirstline = 0 stdin_is_interactive = 1 help = 0 version = 0 saw_inspect_flag = 1 saw_unbuffered_flag = 1 cf = { cf_flags = 0 } #26 0x1d934 in main (argc=4, argv=0xffbef72c) at Modules/python.c:23 No locals. (gdb) 2. Using illegal tag names: Here is the stack trace (no clue what the "warning: Lowest section in ..." is supposed to mean, btw): PYTHONPATH=/home/hjoukl/pydev/PyTAF/pytaf/__PytafTestInstallation_-Q3-ALPHA/lib/python2.3/site-packages/ gdb /apps/pydev/bin/python2.3 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "sparc-sun-solaris2.6"... (gdb) r Starting program: /apps/pydev/bin/python2.3 warning: Lowest section in /lib/libdl.so.1 is .dynamic at 0x94 warning: Lowest section in /lib/libpthread.so.1 is .dynamic at 0x74 Python 2.3.4 (#3, Jul 7 2004, 12:07:09) [GCC 2.95.2 19991024 (release)] on sunos5 Type "help", "copyright", "credits" or "license" for more information. >>> from lxml import etree >>> elt = etree.fromstring('<root><k_status></k_status></root>') >>> elt = etree.fromstring('<root><k+status></k+status></root>') Program received signal SIGSEGV, Segmentation fault. 0xff138dcc in mutex_lock_impl () from /lib/libc.so.1 (gdb) bt #0 0xff138dcc in mutex_lock_impl () from /lib/libc.so.1 #1 0xaa760 in PyThread_release_lock (lock=0x0) at Python/thread_pthread.h:532 #2 0x840c0 in PyEval_ReleaseThread (tstate=0x119cc8) at Python/ceval.c:339 #3 0xa4338 in PyGILState_Release (oldstate=PyGILState_UNLOCKED) at Python/pystate.c:473 #4 0xfef0ceb4 in __pyx_f_5etree__receiveError (__pyx_v_c_log_handler=0x2179e0, __pyx_v_error=0x209f30) at src/lxml/etree.c:15789 #5 0xfecb24b4 in __xmlRaiseError (schannel=0xfef0ce68 <__pyx_f_5etree__receiveError>, channel=0, data=0x2179e0, ctx=0x209db0, nod=0x0, domain=1, code=68, level=XML_ERR_FATAL, file=0x0, line=1, str1=0x0, str2=0x0, str3=0x0, int1=0, col=9, msg=0xfed982d8 "error parsing attribute name\n") at error.c:612 #6 0xfecb65c0 in xmlFatalErrMsg (ctxt=0x209db0, error=XML_ERR_NAME_REQUIRED, msg=0xfed982d8 "error parsing attribute name\n") at parser.c:387 #7 0xfecc5428 in xmlParseAttribute2 (ctxt=0x209db0, pref=0x0, elem=0x261933 "k", prefix=0xffbfec80, value=0xffbfec7c, len=0xffbfec78, alloc=0xffbfec74) at parser.c:7676 #8 0xfecc5864 in xmlParseStartTag2 (ctxt=0x209db0, pref=0xffbfed04, URI=0xffbfed00, tlen=0xffbfecfc) at parser.c:7838 #9 0xfecc719c in xmlParseElement (ctxt=0x209db0) at parser.c:8437 #10 0xfecc6fa4 in xmlParseContent (ctxt=0x209db0) at parser.c:8361 #11 0xfecc7464 in xmlParseElement (ctxt=0x209db0) at parser.c:8521 #12 0xfecc8b9c in xmlParseDocument (ctxt=0x209db0) at parser.c:9129 #13 0xfecce454 in xmlDoRead (ctxt=0x209db0, URL=0x0, encoding=0x0, options=16386, reuse=1) at parser.c:13101 #14 0xfecce80c in xmlCtxtReadMemory (ctxt=0x209db0, buffer=0x250e78 "", size=34, URL=0x0, encoding=0x0, options=16386) at parser.c:13379 #15 0xfeec9bd0 in __pyx_f_5etree_11_BaseParser__parseDoc (__pyx_v_self=0x21a1f0, __pyx_v_c_text=0x21a274 "<root><k+status></k+status></root>", __pyx_v_c_len=34, __pyx_v_c_filename=0x0) at src/lxml/etree.c:20945 #16 0xfeecd438 in __pyx_f_5etree__parseDoc (__pyx_v_text=0x21a260, __pyx_v_filename=0xf7918, __pyx_v_parser=0x21a1f0) at src/lxml/etree.c:22182 #17 0xfeece5d4 in __pyx_f_5etree__parseMemoryDocument (__pyx_v_text=0x21a260, __pyx_v_url=0xf7918, __pyx_v_parser=0x21a1f0) at src/lxml/etree.c:22653 #18 0xfeeaa39c in __pyx_f_5etree_XML (__pyx_self=0x21a1f0, __pyx_args=0xf7918, __pyx_kwds=0x0) at src/lxml/etree.c:9712 #19 0xcda64 in PyCFunction_Call (func=0x18f328, arg=0x2164d0, kw=0x0) at Objects/methodobject.c:77 #20 0x82238 in call_function (pp_stack=0xffbff2d0, oparg=2188496) at Python/ceval.c:3439 #21 0x7fd6c in eval_frame (f=0x179688) at Python/ceval.c:2116 #22 0x81318 in PyEval_EvalCodeEx (co=0x21a2a0, globals=0x0, locals=0x179688, args=0x0, argcount=0, kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0) at Python/ceval.c:2663 #23 0x8413c in PyEval_EvalCode (co=0x21a2a0, globals=0x1349c0, locals=0x1349c0) at Python/ceval.c:537 #24 0xa7164 in run_node (n=0x1236c8, filename=0x21a2a0 "", globals=0x1349c0, locals=0x1349c0, flags=0xffbff64c) at Python/pythonrun.c:1267 #25 0xa53f8 in PyRun_InteractiveOneFlags (fp=0x1236c8, filename=0xd0ed8 "<stdin>", flags=0xffbff64c) at Python/pythonrun.c:757 #26 0xa6a94 in PyRun_InteractiveLoopFlags (fp=0x116008, filename=0xd0ed8 "<stdin>", flags=0xffbff64c) at Python/pythonrun.c:690 #27 0xa683c in PyRun_AnyFileExFlags (fp=0x116008, filename=0xd0ed8 "<stdin>", closeit=0, flags=0xffbff64c) at Python/pythonrun.c:653 #28 0x1e0fc in Py_Main (argc=1, argv=0xffbff734) at Modules/main.c:415 #29 0x1d934 in main (argc=1, argv=0xffbff734) at Modules/python.c:23 (gdb) Both work fine with python2.4, compiled with gcc 3.4.4: 1. $ /apps/pydev/gcc/3.4.4/bin/python2.4 Python 2.4.3 (#1, Apr 12 2006, 11:57:09) [GCC 3.4.4] on sunos5 Type "help", "copyright", "credits" or "license" for more information. >>> from lxml import etree >>> elt = etree.fromstring("""<RvXML xmlns="myURI"></RvXML>""") >>> 2. $ /apps/pydev/gcc/3.4.4/bin/python2.4 Python 2.4.3 (#1, Apr 12 2006, 11:57:09) [GCC 3.4.4] on sunos5 Type "help", "copyright", "credits" or "license" for more information. >>> from lxml import etree >>> elt = etree.fromstring('<root><k_status></k_status></root>') >>> elt = etree.fromstring('<root><k+status></k+status></root>') Traceback (most recent call last): File "<stdin>", line 1, in ? File "etree.pyx", line 1695, in etree.XML File "parser.pxi", line 920, in etree._parseMemoryDocument File "parser.pxi", line 816, in etree._parseDoc File "parser.pxi", line 502, in etree._BaseParser._parseDoc File "parser.pxi", line 605, in etree._handleParseResult File "parser.pxi", line 576, in etree._raiseParseError etree.XMLSyntaxError: line 1: Extra content at the end of the document >>> Greetings, Holger P.S.: I haven't forgotten about the objectify benchmarks, but these days I find it hard dedicating myself to the true cause - but one fine day I hope to come up with them. Der Inhalt dieser E-Mail ist vertraulich. Falls Sie nicht der angegebene Empfänger sind oder falls diese E-Mail irrtümlich an Sie adressiert wurde, verständigen Sie bitte den Absender sofort und löschen Sie die E-Mail sodann. Das unerlaubte Kopieren sowie die unbefugte Übermittlung sind nicht gestattet. Die Sicherheit von Übermittlungen per E-Mail kann nicht garantiert werden. Falls Sie eine Bestätigung wünschen, fordern Sie bitte den Inhalt der E-Mail als Hardcopy an. The contents of this e-mail are confidential. If you are not the named addressee or if this transmission has been addressed to you in error, please notify the sender immediately and then delete this e-mail. Any unauthorized copying and transmission is forbidden. E-Mail transmission cannot be guaranteed to be secure. If verification is required, please request a hard copy version.

2 2

[lxml-dev] getting back RelaxNG tree
by Eric Scheidemantle 16 Nov '06

16 Nov '06

Hello, I'd like to use a set of RelaxNG documents to construct a validation API. The documents will be modular and combined using the externalRef and include tags. I will need a way to access the merged files as if they were one Russian-Doll style file. I see that etree.RelaxNG can be passed an ElementTree object. I assume that etree.parse is not going to resolve RelaxNG references like , and . Does the object etree.RelaxNG return have methods to access the document as if it were built Russian-Doll style, or is it strictly limited to validation? Is there any access to the libxml function xmlRelaxNGDumpTree which I assume may do something like this, but to a file? Ditto for xmlRelaxNGParse? Thank you.

2 2

Re: [lxml-dev] getting back RelaxNG tree
by Eric Scheidemantle 15 Nov '06

15 Nov '06

>No, not currently. Should be easy to add, though. Just add a method (or >property?) to the RelaxNG class that retrieves the in-memory tree. Maybe the >XMLSchema class could do the same? I'd prefer a string result over writing to >a file, BTW. It's easy to write a string to a file, but it's overhead to read >in a file when all you wanted is a string. Certainly, a string is better than writing to a file. >Oh, and: I assume building an ElementTree from the internal RelaxNG schema is >not a good idea, as it could interfere too much with the validation. Copying >them first /might/ work, though. If the RelaxNG class returns a merged XML string, then that could be passed into the ElementTree parse method for navigation. That seems like an elegant solution.

2 1