lxml - The Python XML Toolkit April 2005

lxml@python.org

8 participants
16 discussions

[lxml-dev] Validating xml files against a DTD
by Jeff_Gayle＠sil.org 15 Jun '05

15 Jun '05

I have a dumb question. This is my first experience with libxml2 and lxml and I was wonder how to validate an xml file given a DTD either on the internet or in a catalog (whatever that is). I have read the api.txt file and it has a nice example on how to do this with a RelaxNG file but it does not show an example of how to validate against a DTD. Is it enough to have the declaration in the top of xml file and the parser will automatically validated it? If that is the case, I would think you would want to turn the validation off in certain cases. I briefly looked at the etree.c file but given that I've not done any wrapping of 'C' code, it's kind of hard to figure out the api. ...jeff

3 2

Re: [lxml-dev] Segfault on OS X
by Marc-Antoine Parent 03 May '05

03 May '05

Le 16 avr. 2005, à 09:52, Paul Everitt a écrit : > > Hmm, your etree.so seemed to work! > > Attached is mine. > > --Paul Well, I'll be.... Your etree.so passes all tests on my machine (in either 2.3 or 2.4, which really makes no sense.) (Yes, I am loading the right one. Checked with gdb.) I am beginning to suspect that the problem lies with the DarwinPorts Python... or libxml, or something. BTW, 10.3.9 now includes a nice version of libxml and libxslt. You could try building against those? Marc-Antoine

3 7

[lxml-dev] Test question on Win32 build
by Jeff_Gayle＠sil.org 27 Apr '05

27 Apr '05

After building the latest lxml download, I trying to run the test code, (python test.py in the source directory), and I'm getting a confusing error. I get : 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 "C:\Documents and Settings\All Users\Download\LibXML2libXSLT\lxml\src\lxml\tests\test_etree.py", line 1332, in ? from lxml import etree ImportError: cannot import name etree However, when type 'from lxml import etree' at the python prompt, it imports fine. Anyone have the same problem and know how to fix it? I would to verify that I have a good install and build. And another, should the following be the contents of the /Libs/site-packages/lxml after a successful build of lxml? I had to copy the dll's from the various libxml2/libxslt directories to avoid dll dependency errors when importing the package. /lxml iconv.dll libexslt.dll libxml2.dll libxslt.dll zlib1.dll etree.pyd elementpath.py _elementpath.pyc __init__.py __init__.pyc tests/ test.xml test_broken.xml test_etree.py test_etree.pyc test_unicode.py test_unicode.pyc test_xpathevaluator.py test_xpathevaluator.pyc __init__.py __init__.pyc Thanks in advance...jeff

2 3

[lxml-dev] Problems compiling lxml: "Syntax error in C variable declaration"
by Robin Munn 22 Apr '05

22 Apr '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I just downloaded and installed lxml version 0.5.1 on Mac OS X 10.3. Ran into a small problem at first. When trying to build the 'lxml.etree' extension, Pyrex complained: lxml/src/lxml/xslt.pxd:5:8: Syntax error in C variable declaration ... followed by a ton of errors in etree.pyx. A bit of Googling led me to: http://lists.copyleft.no/pipermail/pyrex/2004-May/000772.html As per Greg Ewing's suggestion in that message, I tried replacing the two "pass" statements in xslt.pyd with "int dummy_var". It worked. I'm using Pyrex 0.9.2.1, and I see in http://www.cosc.canterbury.ac.nz/~greg/python/Pyrex/0.9.3/CHANGES.txt that Pyrex 0.9.3 fixes the bug. So this is really more of a heads-up; the reason I'm sending this to the lxml-dev list is to let you know that since the version of Pyrex that's currently in Fink is 0.9.2.1, you may see other OS X users pop up with this problem. Well, now you know what the cause is. :-) Robin Munn -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCaQNI6OLMk9ZJcBQRAkP0AJ95dHzCuAkVHWpzTgCX/IFs1it9cACdE8rV qXv8+RO71ztWzACjTyrlGFI= =FERj -----END PGP SIGNATURE-----

2 1

[lxml-dev] Segfault on OS X
by Paul Everitt 17 Apr '05

17 Apr '05

Hi all. The following produces a segfault on OS X but not on Ubuntu: >>> from lxml import etree >>> f = open("../data/tmp/content.xml", "r") >>> content = etree.parse(f) >>> f.close() >>> del f, content >>> f = open("../data/tmp/content.xml", "r") >>> content = etree.parse(f) Segmentation fault I did both against the lxml trunk. On OS X it is Python2 .3.5, on Debian, 2.4.x. Is there some special voo-doo I should when closing a parsed document to re-open it? --Paul

3 6

Re: [lxml-dev] Segfault on OS X
by Paul Everitt 16 Apr '05

16 Apr '05

On Apr 15, 2005, at 12:14 AM, Marc-Antoine Parent wrote: > OK... > Would you mind sending us the terminal output of the build process? > (i.e. do a make clean/make test, and copy the terminal contents) > I would like to know what gets picked up. > Also, after the build, please send us the output of > otool -L path/to/lxml/src/lxml/etree.so Sure, thanks for the offer of help! otool output is first: $ otool -L ./build/lib.darwin-7.8.0-Power_Macintosh-2.3/lxml/etree.so ./build/lib.darwin-7.8.0-Power_Macintosh-2.3/lxml/etree.so: /opt/local/lib/libxml2.2.dylib (compatibility version 9.0.0, current version 9.16.0) /opt/local/lib/libxslt.1.dylib (compatibility version 3.0.0, current version 3.12.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 71.1.1) Next, build: socrates:~/sandboxes/lxml paul$ python ./setup.py build running build running build_py creating build creating build/lib.darwin-7.8.0-Power_Macintosh-2.3 creating build/lib.darwin-7.8.0-Power_Macintosh-2.3/lxml creating build/lib.darwin-7.8.0-Power_Macintosh-2.3/lxml/tests copying src/lxml/tests/__init__.py -> build/lib.darwin-7.8.0-Power_Macintosh-2.3/lxml/tests copying src/lxml/tests/test_etree.py -> build/lib.darwin-7.8.0-Power_Macintosh-2.3/lxml/tests copying src/lxml/tests/test_unicode.py -> build/lib.darwin-7.8.0-Power_Macintosh-2.3/lxml/tests copying src/lxml/tests/test_xpathevaluator.py -> build/lib.darwin-7.8.0-Power_Macintosh-2.3/lxml/tests copying src/lxml/__init__.py -> build/lib.darwin-7.8.0-Power_Macintosh-2.3/lxml copying src/lxml/_elementpath.py -> build/lib.darwin-7.8.0-Power_Macintosh-2.3/lxml running build_ext building 'lxml.etree' extension creating build/temp.darwin-7.8.0-Power_Macintosh-2.3 creating build/temp.darwin-7.8.0-Power_Macintosh-2.3/src creating build/temp.darwin-7.8.0-Power_Macintosh-2.3/src/lxml gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd -fno-common -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I/opt/local/include/libxml2 -I/opt/local/include -I/opt/local/include/python2.3 -c src/lxml/etree.c -o build/temp.darwin-7.8.0-Power_Macintosh-2.3/src/lxml/etree.o -w gcc -L/opt/local/lib -bundle -undefined dynamic_lookup build/temp.darwin-7.8.0-Power_Macintosh-2.3/src/lxml/etree.o -L/opt/local/lib -L/opt/local/lib -lxml2 -lxslt -o build/lib.darwin-7.8.0-Power_Macintosh-2.3/lxml/etree.so creating build/lib.darwin-7.8.0-Power_Macintosh-2.3/.svn copying src/.svn/README.txt -> build/lib.darwin-7.8.0-Power_Macintosh-2.3/.svn creating build/lib.darwin-7.8.0-Power_Macintosh-2.3/lxml/.svn copying src/lxml/.svn/README.txt -> build/lib.darwin-7.8.0-Power_Macintosh-2.3/lxml/.svn copying src/lxml/tests/test.xml -> build/lib.darwin-7.8.0-Power_Macintosh-2.3/lxml/tests copying src/lxml/tests/test_broken.xml -> build/lib.darwin-7.8.0-Power_Macintosh-2.3/lxml/tests creating build/lib.darwin-7.8.0-Power_Macintosh-2.3/lxml/tests/.svn copying src/lxml/tests/.svn/README.txt -> build/lib.darwin-7.8.0-Power_Macintosh-2.3/lxml/tests/.svn socrates:~/sandboxes/lxml paul$ sudo python ./setup.py install running install running build running build_py running build_ext running install_lib copying build/lib.darwin-7.8.0-Power_Macintosh-2.3/lxml/etree.so -> /opt/local/lib/python2.3/site-packages/lxml socrates:~/sandboxes/lxml paul$ socrates:~/sandboxes/lxml paul$ socrates:~/sandboxes/lxml paul$ python Python 2.3.5 (#1, Mar 6 2005, 18:54:59) [GCC 3.3 20030304 (Apple Computer, Inc. build 1671)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> socrates:~/sandboxes/lxml paul$ cd socrates:~ paul$ cd projects/ socrates:~/projects paul$ cd plonemarketing/ socrates:~/projects/plonemarketing paul$ ls PloneMarketing doc schemas data models templates socrates:~/projects/plonemarketing paul$ cd PloneMarketing/ socrates:~/projects/plonemarketing/PloneMarketing paul$ python Python 2.3.5 (#1, Mar 6 2005, 18:54:59) [GCC 3.3 20030304 (Apple Computer, Inc. build 1671)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from lxml import etree >>> f = open ("../data/tmp/content.xml", "r") >>> content = etree.parse(f) >>> f.close() >>> del f, content >>> f = open ("../data/tmp/content.xml", "r") >>> f.close() >>> f = open ("../data/tmp/content.xml", "r") >>> content = etree.parse(f) Segmentation fault

3 5

Re: [lxml-dev] Segfault on OS X
by Marc-Antoine Parent 15 Apr '05

15 Apr '05

OK... Would you mind sending us the terminal output of the build process? (i.e. do a make clean/make test, and copy the terminal contents) I would like to know what gets picked up. Also, after the build, please send us the output of otool -L path/to/lxml/src/lxml/etree.so Thank you, Marc-Antoine

1 0

Re: [lxml-dev] Segfault on OS X
by Marc-Antoine Parent 14 Apr '05

14 Apr '05

Sorry, I forgot to copy the list again. (Could you set the reply-to field in the listserv?) > I've extended the use of the guessing code in setup.py to also extract > the library information. Try the trunk and see whether that helps? It does. However, I noticed in the compilation process, the guessing code only looks at xml2-config, not at xslt-config. Somehow, the compilation still works without -I/usr/local/lib, but I am not sure where it finds the libxsl include files, and I do not like this. Would you think it appropriate to add the result of xslt-config --cflags to the libraries? P.S. I just checked, and it seems gcc knows about looking for xsl in /usr/local/include. So the issue is not that /usr/local/lib is not known, but that it may have lower priority than /usr/lib. Still, I would recommend getting the output of xslt-config --cflags , in case of non-standard installs. Marc-Antoine

2 1

Re: [lxml-dev] Segfault on OS X
by Martijn Faassen 14 Apr '05

14 Apr '05

Hey, [this was mailed to just me by mistake, presmably, so cc to the list] Marc-Antoine Parent wrote: >> I've extended the use of the guessing code in setup.py to also extract >> the library information. Try the trunk and see whether that helps? > > It does. However, I noticed in the compilation process, the guessing > code only looks at xml2-config, not at xslt-config. Somehow, the > compilation still works without -I/usr/local/lib, but I am not sure > where it finds the libxsl include files, and I do not like this. Would > you think it appropriate to add the result of xslt-config --cflags to > the libraries? And the result of xslt-config --libs, presumably. Possibly there'll be more output from those commands that's needed later, for other platforms. It'll be one heck of a customized setup.py, but it seems inevitable, unfortunately. I wonder what happens on Windows.. Do you want to hack something up? I'm not sure when I'll time to get around to this. Regards, Martijn

1 0

Fwd: [lxml-dev] Segfault on OS X
by Marc-Antoine Parent 13 Apr '05

13 Apr '05

FYI, I also have the same problem. I ran the tests through gdb, and this is what I get. xmllint: using libxml version 20619 gdb python GNU gdb 5.3-20030128 (Apple version gdb-330.1) (Fri Jul 16 21:42:28 GMT 2004) Copyright 2003 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 "powerpc-apple-darwin". Reading symbols for shared libraries ... done (gdb) set args test.py -p -v (gdb) run Starting program: /usr/bin/python test.py -p -v Reading symbols for shared libraries . done ... Reading symbols for shared libraries . done 3/238 ( 1.3%): test_attribute_items (lxml.tests.test_etree.ETreeTestCase) Program received signal EXC_BAD_ACCESS, Could not access memory. 0x94ad072c in xmlDictOwns () (gdb) bt #0 0x94ad072c in xmlDictOwns () #1 0x94a53068 in xmlFreeNodeList () #2 0x94a518f8 in xmlFreeProp () #3 0x94a51810 in xmlFreePropList () #4 0x94a53028 in xmlFreeNodeList () #5 0x94a504f4 in xmlFreeDoc () #6 0x004f4230 in __pyx_tp_dealloc_5etree__DocumentBase (o=0x3e110) at src/lxml/etree.c:354 #7 0x004f43fc in __pyx_tp_dealloc_5etree__NodeBase (o=0xd4e8) at src/lxml/etree.c:9688 #8 0x10024898 in frame_dealloc (f=0x124ae0) at Objects/frameobject.c:394 #9 0x1007cab8 in fast_function (func=0x121d30, pp_stack=0xc, n=7, na=5194268, nk=1187120) at Python/ceval.c:3632 #10 0x1007c908 in call_function (pp_stack=0xbfffdfcc, oparg=1255136) at Python/ceval.c:3568 #11 0x1007a384 in PyEval_EvalFrame (f=0x83d810) at Python/ceval.c:2163 #12 0x1007b4c8 in PyEval_EvalCodeEx (co=0x0, globals=0x1326e0, locals=0x42657475, args=0x10078444, argcount=1049072, kws=0x1007a374, kwcount=1, defs=0x83d96c, defcount=1, closure=0x0) at Python/ceval.c:2730 #13 0x100264b8 in function_call (func=0x10c809, arg=0x1001f0, kw=0x83d810) at Objects/funcobject.c:548 #14 0x1000c58c in PyObject_Call (func=0x121d30, arg=0x1326e0, kw=0x0) at Objects/abstract.c:1751 #15 0x1007d078 in ext_do_call (func=0x6d430, pp_stack=0xbfffe290, flags=269601980, na=1, nk=0) at Python/ceval.c:3824 #16 0x1007a474 in PyEval_EvalFrame (f=0x116730) at Python/ceval.c:2203 #17 0x1007b4c8 in PyEval_EvalCodeEx (co=0x11688c, globals=0x1326e0, locals=0x42657475, args=0xa30d0, argcount=1049072, kws=0x1007a374, kwcount=1, defs=0x83d96c, defcount=0, closure=0x0) at Python/ceval.c:2730 #18 0x100264b8 in function_call (func=0x627eb, arg=0x1001f0, kw=0x116730) at Objects/funcobject.c:548 #19 0x1000c58c in PyObject_Call (func=0x121d30, arg=0x1326e0, kw=0x0) at Objects/abstract.c:1751 #20 0x10015ccc in instancemethod_call (func=0x6d470, arg=0x567878, kw=0x0) at Objects/classobject.c:2431 #21 0x1000c58c in PyObject_Call (func=0x121d30, arg=0x1326e0, kw=0x0) at Objects/abstract.c:1751 #22 0x1005959c in slot_tp_call (self=0xa30d0, args=0x54c570, kwds=0x0) at Objects/typeobject.c:4526 #23 0x1000c58c in PyObject_Call (func=0x121d30, arg=0x1326e0, kw=0x0) at Objects/abstract.c:1751 #24 0x1007cc28 in do_call (func=0xa30d0, pp_stack=0xa30d0, na=0, nk=1049072) at Python/ceval.c:3755 #25 0x1007c920 in call_function (pp_stack=0x0, oparg=1255136) at Python/ceval.c:3570 #26 0x1007a384 in PyEval_EvalFrame (f=0x109bc0) at Python/ceval.c:2163 #27 0x1007b4c8 in PyEval_EvalCodeEx (co=0x1, globals=0x1326e0, locals=0x42657475, args=0x10078444, argcount=1049072, kws=0x1007a374, kwcount=1, defs=0x83d96c, defcount=0, closure=0x0) at Python/ceval.c:2730 #28 0x100264b8 in function_call (func=0x2092dc, arg=0x1001f0, kw=0x109bc0) at Objects/funcobject.c:548 #29 0x1000c58c in PyObject_Call (func=0x121d30, arg=0x1326e0, kw=0x0) at Objects/abstract.c:1751 #30 0x1007d078 in ext_do_call (func=0x6d8b0, pp_stack=0xbfffebd0, flags=269601980, na=1, nk=0) at Python/ceval.c:3824 #31 0x1007a474 in PyEval_EvalFrame (f=0x107160) at Python/ceval.c:2203 #32 0x1007b4c8 in PyEval_EvalCodeEx (co=0x1072bc, globals=0x1326e0, locals=0x42657475, args=0x55bc70, argcount=1049072, kws=0x1007a374, kwcount=1, defs=0x83d96c, defcount=0, closure=0x0) at Python/ceval.c:2730 #33 0x100264b8 in function_call (func=0x62cc3, arg=0x1001f0, kw=0x107160) at Objects/funcobject.c:548 #34 0x1000c58c in PyObject_Call (func=0x121d30, arg=0x1326e0, kw=0x0) at Objects/abstract.c:1751 #35 0x10015ccc in instancemethod_call (func=0x6d8f0, arg=0xd3350, kw=0x0) at Objects/classobject.c:2431 #36 0x1000c58c in PyObject_Call (func=0x121d30, arg=0x1326e0, kw=0x0) at Objects/abstract.c:1751 #37 0x1005959c in slot_tp_call (self=0x55bc70, args=0x565690, kwds=0x0) at Objects/typeobject.c:4526 #38 0x1000c58c in PyObject_Call (func=0x121d30, arg=0x1326e0, kw=0x0) at Objects/abstract.c:1751 #39 0x1007cc28 in do_call (func=0x55bc70, pp_stack=0x55bc70, na=0, nk=1049072) at Python/ceval.c:3755 #40 0x1007c920 in call_function (pp_stack=0x0, oparg=1255136) at Python/ceval.c:3570 #41 0x1007a384 in PyEval_EvalFrame (f=0x104c50) at Python/ceval.c:2163 #42 0x1007ca80 in fast_function (func=0x121d30, pp_stack=0x104dc8, n=268928068, na=5194268, nk=1187120) at Python/ceval.c:3629 #43 0x1007c908 in call_function (pp_stack=0xbffff3fc, oparg=1255136) at Python/ceval.c:3568 #44 0x1007a384 in PyEval_EvalFrame (f=0x842c10) at Python/ceval.c:2163 #45 0x1007ca80 in fast_function (func=0x121d30, pp_stack=0x842dc8, n=268928068, na=5194268, nk=1187120) at Python/ceval.c:3629 #46 0x1007c908 in call_function (pp_stack=0xbffff5ac, oparg=1255136) at Python/ceval.c:3568 #47 0x1007a384 in PyEval_EvalFrame (f=0x108850) at Python/ceval.c:2163 #48 0x1007b4c8 in PyEval_EvalCodeEx (co=0x1, globals=0x1326e0, locals=0x42657475, args=0x10078444, argcount=1049072, kws=0x1007a374, kwcount=1, defs=0x83d96c, defcount=0, closure=0x0) at Python/ceval.c:2730 #49 0x1007e8bc in PyEval_EvalCode (co=0x121d30, globals=0x1326e0, locals=0x0) at Python/ceval.c:484 #50 0x100b3124 in run_node (n=0x10078444, filename=0x1326e0 "Alpha", globals=0x1, locals=0x1089a4, flags=0x0) at Python/pythonrun.c:1265 #51 0x100b28b0 in PyRun_SimpleFileExFlags (fp=0xa0009818, filename=0xbffffa10 "test.py", closeit=1083472, flags=0x10b849) at Python/pythonrun.c:860 #52 0x100bf884 in Py_Main (argc=129616, argv=0xbffffa13) at Modules/main.c:484 #53 0x000018d0 in _start (argc=129616, argv=0xa0009818, envp=0xbffffa13) at /SourceCache/Csu/Csu-47/crt.c:267 #54 0x8fe1a558 in __dyld__dyld_start ()

2 6

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

lxml - The Python XML Toolkit April 2005