blob: 00b885d52fcd8bd385413ab21e09420813b68093 [file] [log] [blame]
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00001<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
2<html>
3<head>
4<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
5<style type="text/css"><!--
Daniel Veillard373a4752002-02-21 14:46:29 +00006TD {font-family: Verdana,Arial,Helvetica}
7BODY {font-family: Verdana,Arial,Helvetica; margin-top: 2em; margin-left: 0em; margin-right: 0em}
8H1 {font-family: Verdana,Arial,Helvetica}
9H2 {font-family: Verdana,Arial,Helvetica}
10H3 {font-family: Verdana,Arial,Helvetica}
Daniel Veillard6dbcaf82002-02-20 14:37:47 +000011A:link, A:visited, A:active { text-decoration: underline }
12--></style>
13<title>Python and bindings</title>
14</head>
15<body bgcolor="#8b7765" text="#000000" link="#000000" vlink="#000000">
16<table border="0" width="100%" cellpadding="5" cellspacing="0" align="center"><tr>
17<td width="180">
18<a href="http://www.gnome.org/"><img src="smallfootonly.gif" alt="Gnome Logo"></a><a href="http://www.w3.org/Status"><img src="w3c.png" alt="W3C Logo"></a><a href="http://www.redhat.com/"><img src="redhat.gif" alt="Red Hat Logo"></a>
19</td>
20<td><table border="0" width="90%" cellpadding="2" cellspacing="0" align="center" bgcolor="#000000"><tr><td><table width="100%" border="0" cellspacing="1" cellpadding="3" bgcolor="#fffacd"><tr><td align="center">
21<h1>The XML C library for Gnome</h1>
22<h2>Python and bindings</h2>
23</td></tr></table></td></tr></table></td>
24</tr></table>
25<table border="0" cellpadding="4" cellspacing="0" width="100%" align="center"><tr><td bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="2" width="100%"><tr>
26<td valign="top" width="200" bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="1" width="100%" bgcolor="#000000"><tr><td>
27<table width="100%" border="0" cellspacing="1" cellpadding="3">
28<tr><td colspan="1" bgcolor="#eecfa1" align="center"><center><b>Main Menu</b></center></td></tr>
29<tr><td bgcolor="#fffacd"><ul>
30<li><a href="index.html">Home</a></li>
31<li><a href="intro.html">Introduction</a></li>
32<li><a href="FAQ.html">FAQ</a></li>
33<li><a href="docs.html">Documentation</a></li>
34<li><a href="bugs.html">Reporting bugs and getting help</a></li>
35<li><a href="help.html">How to help</a></li>
36<li><a href="downloads.html">Downloads</a></li>
37<li><a href="news.html">News</a></li>
38<li><a href="XMLinfo.html">XML</a></li>
39<li><a href="XSLT.html">XSLT</a></li>
40<li><a href="python.html">Python and bindings</a></li>
41<li><a href="architecture.html">libxml architecture</a></li>
42<li><a href="tree.html">The tree output</a></li>
43<li><a href="interface.html">The SAX interface</a></li>
44<li><a href="xmldtd.html">Validation &amp; DTDs</a></li>
45<li><a href="xmlmem.html">Memory Management</a></li>
46<li><a href="encoding.html">Encodings support</a></li>
47<li><a href="xmlio.html">I/O Interfaces</a></li>
48<li><a href="catalog.html">Catalog support</a></li>
49<li><a href="library.html">The parser interfaces</a></li>
50<li><a href="entities.html">Entities or no entities</a></li>
51<li><a href="namespaces.html">Namespaces</a></li>
52<li><a href="upgrade.html">Upgrading 1.x code</a></li>
53<li><a href="threads.html">Thread safety</a></li>
54<li><a href="DOM.html">DOM Principles</a></li>
55<li><a href="example.html">A real example</a></li>
56<li><a href="contribs.html">Contributions</a></li>
57<li>
58<a href="xml.html">flat page</a>, <a href="site.xsl">stylesheet</a>
59</li>
60</ul></td></tr>
61</table>
62<table width="100%" border="0" cellspacing="1" cellpadding="3">
63<tr><td colspan="1" bgcolor="#eecfa1" align="center"><center><b>API Indexes</b></center></td></tr>
64<tr><td bgcolor="#fffacd"><ul>
65<li><a href="APIchunk0.html">Alphabetic</a></li>
66<li><a href="APIconstructors.html">Constructors</a></li>
67<li><a href="APIfunctions.html">Functions/Types</a></li>
68<li><a href="APIfiles.html">Modules</a></li>
69<li><a href="APIsymbols.html">Symbols</a></li>
70</ul></td></tr>
71</table>
72<table width="100%" border="0" cellspacing="1" cellpadding="3">
73<tr><td colspan="1" bgcolor="#eecfa1" align="center"><center><b>Related links</b></center></td></tr>
74<tr><td bgcolor="#fffacd"><ul>
75<li><a href="http://mail.gnome.org/archives/xml/">Mail archive</a></li>
76<li><a href="http://xmlsoft.org/XSLT/">XSLT libxslt</a></li>
77<li><a href="http://phd.cs.unibo.it/gdome2/">DOM gdome2</a></li>
78<li><a href="ftp://xmlsoft.org/">FTP</a></li>
79<li><a href="http://www.fh-frankfurt.de/~igor/projects/libxml/">Windows binaries</a></li>
80<li><a href="http://garypennington.net/libxml2/">Solaris binaries</a></li>
81<li><a href="http://bugzilla.gnome.org/buglist.cgi?product=libxml">Bug Tracker</a></li>
82</ul></td></tr>
83</table>
84</td></tr></table></td>
85<td valign="top" bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="1" width="100%"><tr><td><table border="0" cellspacing="0" cellpadding="1" width="100%" bgcolor="#000000"><tr><td><table border="0" cellpadding="3" cellspacing="1" width="100%"><tr><td bgcolor="#fffacd">
86<p>There is a number of language bindings and wrappers available for libxml2,
87the list below is not exhaustive. Please contact the <a href="http://mail.gnome.org/mailman/listinfo/xml-bindings">xml-bindings@gnome.org</a>
88(<a href="http://mail.gnome.org/archives/xml-bindings/">archives</a>) in
89order to get updates to this list or to discuss the specific topic of libxml2
90or libxslt wrappers or bindings:</p>
91<ul>
92<li>
93<a href="mailto:ari@lusis.org">Ari Johnson</a>
94 provides a C++ wrapper for libxml:<br>
95 Website: <a href="http://lusis.org/~ari/xml++/">http://lusis.org/~ari/xml++/</a><br>
96 Download: <a href="http://lusis.org/~ari/xml++/libxml++.tar.gz">http://lusis.org/~ari/xml++/libxml++.tar.gz</a>
97</li>
98<li>There is another <a href="http://libgdome-cpp.berlios.de/">C++ wrapper
99 based on the gdome2 </a>bindings maintained by Tobias Peters.</li>
100<li>
101<a href="http://mail.gnome.org/archives/xml/2001-March/msg00014.html">Matt
102 Sergeant</a>
103 developped <a href="http://axkit.org/download/">XML::LibXSLT</a>, a perl
104 wrapper for libxml2/libxslt as part of the <a href="http://axkit.com/">AxKit XML application server</a>
105</li>
106<li>
107<a href="mailto:dkuhlman@cutter.rexx.com">Dave Kuhlman</a>
108 provides and earlier version of the libxml/libxslt <a href="http://www.rexx.com/~dkuhlman">wrappers for Python</a>
109</li>
110<li>Petr Kozelka provides <a href="http://sourceforge.net/projects/libxml2-pas">Pascal units to glue
111 libxml2</a> with Kylix, Delphi and other Pascal compilers</li>
112<li>Wai-Sun &quot;Squidster&quot; Chia provides <a href="http://www.rubycolor.org/arc/redist/">bindings for Ruby</a> and
113 libxml2 bindings are also available in Ruby through the <a href="http://libgdome-ruby.berlios.de/">libgdome-ruby</a> module
114 maintained by Tobias Peters.</li>
Daniel Veillardb9e469a2002-02-21 12:08:42 +0000115<li>Steve Ball and contributors maintains
116 <a href="http://tclxml.sourceforge.net/">libxml2 and libxslt bindings for
117 Tcl</a>
118</li>
119<li>There is support for libxml2 in the DOM module of PHP.
120</li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000121</ul>
122<p>The distribution includes a set of Python bindings, which are garanteed to
123be maintained as part of the library in the future, though the Python
Daniel Veillard0b79dfe2002-02-23 13:02:31 +0000124interface have not yet reached the maturity of the C API.</p>
125<p>To install the Python bindings there are 2 options:
126</p>
127<ul>
128<li> If you use an RPM based distribution, simply install the
129<a href="http://rpmfind.net/linux/rpm2html/search.php?query=libxml2-python">libxml2-python RPM</a> (and if needed the
130<a href="http://rpmfind.net/linux/rpm2html/search.php?query=libxslt-python">libxslt-python RPM</a>).
131</li>
132<li> Otherwise use the <a href="ftp://xmlsoft.org/python/">libxml2-python
133module distribution</a> corresponding to your installed version of libxml2
134and libxslt. Note that to install it you will need both libxml2 and libxslt
135installed and run &quot;python setup.py build install&quot; in the module tree.
136</li>
137</ul>
138<p>The distribution
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000139includes a set of examples and regression tests for the python bindings in
140the <code>python/tests</code> directory. Here are some excepts from those
141tests:</p>
142<h3>tst.py:</h3>
143<p>This is a basic test of the file interface and DOM navigation:</p>
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000144<pre>import libxml2
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000145
146doc = libxml2.parseFile(&quot;tst.xml&quot;)
147if doc.name != &quot;tst.xml&quot;:
148 print &quot;doc.name failed&quot;
149 sys.exit(1)
150root = doc.children
151if root.name != &quot;doc&quot;:
152 print &quot;root.name failed&quot;
153 sys.exit(1)
154child = root.children
155if child.name != &quot;foo&quot;:
156 print &quot;child.name failed&quot;
157 sys.exit(1)
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000158doc.freeDoc()</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000159<p>The Python module is called libxml2, parseFile is the equivalent of
160xmlParseFile (most of the bindings are automatically generated, and the xml
161prefix is removed and the casing convention are kept). All node seen at the
162binding level share the same subset of accesors:</p>
163<ul>
164<li>
165<code>name</code>
166 : returns the node name</li>
167<li>
168<code>type</code>
169 : returns a string indicating the node typ<code>e</code>
170</li>
171<li>
172<code>content</code>
173 : returns the content of the node, it is based on xmlNodeGetContent() and
174 hence is recursive.</li>
175<li>
176<code>parent</code>
177 , <code>children</code>, <code>last</code>, <code>next</code>,
178 <code>prev</code>, <code>doc</code>, <code>properties</code>: pointing to
179 the associated element in the tree, those may return None in case no such
180 link exists.</li>
181</ul>
182<p>Also note the need to explicitely deallocate documents with freeDoc() .
183Reference counting for libxml2 trees would need quite a lot of work to
184function properly, and rather than risk memory leaks if not implemented
185correctly it sounds safer to have an explicit function to free a tree. The
186wrapper python objects like doc, root or child are them automatically garbage
187collected.</p>
188<h3>validate.py:</h3>
189<p>This test check the validation interfaces and redirection of error
190messages:</p>
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000191<pre>import libxml2
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000192
193#desactivate error messages from the validation
194def noerr(ctx, str):
195 pass
196
197libxml2.registerErrorHandler(noerr, None)
198
199ctxt = libxml2.createFileParserCtxt(&quot;invalid.xml&quot;)
200ctxt.validate(1)
201ctxt.parseDocument()
202doc = ctxt.doc()
203valid = ctxt.isValid()
204doc.freeDoc()
205if valid != 0:
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000206 print &quot;validity chec failed&quot;</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000207<p>The first thing to notice is the call to registerErrorHandler(), it
208defines a new error handler global to the library. It is used to avoid seeing
209the error messages when trying to validate the invalid document.</p>
210<p>The main interest of that test is the creation of a parser context with
211createFileParserCtxt() and how the behaviour can be changed before calling
212parseDocument() . Similary the informations resulting from the parsing phase
213are also available using context methods.</p>
214<p>Contexts like nodes are defined as class and the libxml2 wrappers maps the
215C function interfaces in terms of objects method as much as possible. The
216best to get a complete view of what methods are supported is to look at the
217libxml2.py module containing all the wrappers.</p>
218<h3>push.py:</h3>
219<p>This test show how to activate the push parser interface:</p>
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000220<pre>import libxml2
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000221
222ctxt = libxml2.createPushParser(None, &quot;&lt;foo&quot;, 4, &quot;test.xml&quot;)
223ctxt.parseChunk(&quot;/&gt;&quot;, 2, 1)
224doc = ctxt.doc()
225
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000226doc.freeDoc()</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000227<p>The context is created with a speciall call based on the
228xmlCreatePushParser() from the C library. The first argument is an optional
229SAX callback object, then the initial set of data, the lenght and the name of
230the resource in case URI-References need to be computed by the parser.</p>
231<p>Then the data are pushed using the parseChunk() method, the last call
232setting the thrird argument terminate to 1.</p>
233<h3>pushSAX.py:</h3>
234<p>this test show the use of the event based parsing interfaces. In this case
235the parser does not build a document, but provides callback information as
236the parser makes progresses analyzing the data being provided:</p>
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000237<pre>import libxml2
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000238log = &quot;&quot;
239
240class callback:
241 def startDocument(self):
242 global log
243 log = log + &quot;startDocument:&quot;
244
245 def endDocument(self):
246 global log
247 log = log + &quot;endDocument:&quot;
248
249 def startElement(self, tag, attrs):
250 global log
251 log = log + &quot;startElement %s %s:&quot; % (tag, attrs)
252
253 def endElement(self, tag):
254 global log
255 log = log + &quot;endElement %s:&quot; % (tag)
256
257 def characters(self, data):
258 global log
259 log = log + &quot;characters: %s:&quot; % (data)
260
261 def warning(self, msg):
262 global log
263 log = log + &quot;warning: %s:&quot; % (msg)
264
265 def error(self, msg):
266 global log
267 log = log + &quot;error: %s:&quot; % (msg)
268
269 def fatalError(self, msg):
270 global log
271 log = log + &quot;fatalError: %s:&quot; % (msg)
272
273handler = callback()
274
275ctxt = libxml2.createPushParser(handler, &quot;&lt;foo&quot;, 4, &quot;test.xml&quot;)
276chunk = &quot; url='tst'&gt;b&quot;
277ctxt.parseChunk(chunk, len(chunk), 0)
278chunk = &quot;ar&lt;/foo&gt;&quot;
279ctxt.parseChunk(chunk, len(chunk), 1)
280
Daniel Veillardfcbfa2d2002-02-21 17:54:27 +0000281reference = &quot;startDocument:startElement foo {'url': 'tst'}:&quot; + \
282 &quot;characters: bar:endElement foo:endDocument:&quot;
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000283if log != reference:
284 print &quot;Error got: %s&quot; % log
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000285 print &quot;Exprected: %s&quot; % reference</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000286<p>The key object in that test is the handler, it provides a number of entry
287points which can be called by the parser as it makes progresses to indicate
288the information set obtained. The full set of callback is larger than what
289the callback class in that specific example implements (see the SAX
290definition for a complete list). The wrapper will only call those supplied by
291the object when activated. The startElement receives the names of the element
292and a dictionnary containing the attributes carried by this element.</p>
293<p>Also note that the reference string generated from the callback shows a
294single character call even though the string &quot;bar&quot; is passed to the parser
295from 2 different call to parseChunk()</p>
296<h3>xpath.py:</h3>
297<p>This is a basic test of XPath warppers support</p>
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000298<pre>import libxml2
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000299
300doc = libxml2.parseFile(&quot;tst.xml&quot;)
301ctxt = doc.xpathNewContext()
302res = ctxt.xpathEval(&quot;//*&quot;)
303if len(res) != 2:
304 print &quot;xpath query: wrong node set size&quot;
305 sys.exit(1)
306if res[0].name != &quot;doc&quot; or res[1].name != &quot;foo&quot;:
307 print &quot;xpath query: wrong node set value&quot;
308 sys.exit(1)
309doc.freeDoc()
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000310ctxt.xpathFreeContext()</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000311<p>This test parses a file, then create an XPath context to evaluate XPath
312expression on it. The xpathEval() method execute an XPath query and returns
313the result mapped in a Python way. String and numbers are natively converted,
314and node sets are returned as a tuple of libxml2 Python nodes wrappers. Like
315the document, the XPath context need to be freed explicitely, also not that
316the result of the XPath query may point back to the document tree and hence
317the document must be freed after the result of the query is used.</p>
318<h3>xpathext.py:</h3>
319<p>This test shows how to extend the XPath engine with functions written in
320python:</p>
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000321<pre>import libxml2
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000322
323def foo(ctx, x):
324 return x + 1
325
326doc = libxml2.parseFile(&quot;tst.xml&quot;)
327ctxt = doc.xpathNewContext()
328libxml2.registerXPathFunction(ctxt._o, &quot;foo&quot;, None, foo)
329res = ctxt.xpathEval(&quot;foo(1)&quot;)
330if res != 2:
331 print &quot;xpath extension failure&quot;
332doc.freeDoc()
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000333ctxt.xpathFreeContext()</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000334<p>Note how the extension function is registered with the context (but that
335part is not yet finalized, ths may change slightly in the future).</p>
336<h3>tstxpath.py:</h3>
337<p>This test is similar to the previousone but shows how the extension
338function can access the XPath evaluation context:</p>
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000339<pre>def foo(ctx, x):
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000340 global called
341
342 #
343 # test that access to the XPath evaluation contexts
344 #
345 pctxt = libxml2.xpathParserContext(_obj=ctx)
346 ctxt = pctxt.context()
347 called = ctxt.function()
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000348 return x + 1</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000349<p>All the interfaces around the XPath parser(or rather evaluation) context
350are not finalized, but it should be sufficient to do contextual work at the
351evaluation point.</p>
352<h3>Memory debugging:</h3>
353<p>last but not least, all tests starts with the following prologue:</p>
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000354<pre>#memory debug specific
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000355libxml2.debugMemory(1)
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000356</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000357<p>and ends with the following epilogue:</p>
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000358<pre>#memory debug specific
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000359libxml2.cleanupParser()
360if libxml2.debugMemory(1) == 0:
361 print &quot;OK&quot;
362else:
363 print &quot;Memory leak %d bytes&quot; % (libxml2.debugMemory(1))
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000364 libxml2.dumpMemory()</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000365<p>Those activate the memory debugging interface of libxml2 where all
366alloacted block in the library are tracked. The prologue then cleans up the
367library state and checks that all allocated memory has been freed. If not it
368calls dumpMemory() which saves that list in a <code>.memdump</code> file.</p>
369<p><a href="bugs.html">Daniel Veillard</a></p>
370</td></tr></table></td></tr></table></td></tr></table></td>
371</tr></table></td></tr></table>
372</body>
373</html>