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