| Daniel Veillard | 6dbcaf8 | 2002-02-20 14:37:47 +0000 | [diff] [blame] | 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 | <style type="text/css"><!-- |
| 6 | TD {font-size: 14pt; font-family: Verdana,Arial,Helvetica} |
| 7 | BODY {font-size: 14pt; font-family: Verdana,Arial,Helvetica; margin-top: 2em; margin-left: 0em; margin-right: 0em} |
| 8 | H1 {font-size: 20pt; font-family: Verdana,Arial,Helvetica} |
| 9 | H2 {font-size: 18pt; font-family: Verdana,Arial,Helvetica} |
| 10 | H3 {font-size: 16pt; font-family: Verdana,Arial,Helvetica} |
| 11 | A: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 & 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, |
| 87 | the 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 |
| 89 | order to get updates to this list or to discuss the specific topic of libxml2 |
| 90 | or 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 "Squidster" 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 Veillard | b9e469a | 2002-02-21 12:08:42 +0000 | [diff] [blame^] | 115 | <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 Veillard | 6dbcaf8 | 2002-02-20 14:37:47 +0000 | [diff] [blame] | 121 | </ul> |
| 122 | <p>The distribution includes a set of Python bindings, which are garanteed to |
| 123 | be maintained as part of the library in the future, though the Python |
| 124 | interface have not yet reached the maturity of the C API. The distribution |
| 125 | includes a set of examples and regression tests for the python bindings in |
| 126 | the <code>python/tests</code> directory. Here are some excepts from those |
| 127 | tests:</p> |
| 128 | <h3>tst.py:</h3> |
| 129 | <p>This is a basic test of the file interface and DOM navigation:</p> |
| 130 | <pre>import libxml2 |
| 131 | |
| 132 | doc = libxml2.parseFile("tst.xml") |
| 133 | if doc.name != "tst.xml": |
| 134 | print "doc.name failed" |
| 135 | sys.exit(1) |
| 136 | root = doc.children |
| 137 | if root.name != "doc": |
| 138 | print "root.name failed" |
| 139 | sys.exit(1) |
| 140 | child = root.children |
| 141 | if child.name != "foo": |
| 142 | print "child.name failed" |
| 143 | sys.exit(1) |
| 144 | doc.freeDoc()</pre> |
| 145 | <p>The Python module is called libxml2, parseFile is the equivalent of |
| 146 | xmlParseFile (most of the bindings are automatically generated, and the xml |
| 147 | prefix is removed and the casing convention are kept). All node seen at the |
| 148 | binding level share the same subset of accesors:</p> |
| 149 | <ul> |
| 150 | <li> |
| 151 | <code>name</code> |
| 152 | : returns the node name</li> |
| 153 | <li> |
| 154 | <code>type</code> |
| 155 | : returns a string indicating the node typ<code>e</code> |
| 156 | </li> |
| 157 | <li> |
| 158 | <code>content</code> |
| 159 | : returns the content of the node, it is based on xmlNodeGetContent() and |
| 160 | hence is recursive.</li> |
| 161 | <li> |
| 162 | <code>parent</code> |
| 163 | , <code>children</code>, <code>last</code>, <code>next</code>, |
| 164 | <code>prev</code>, <code>doc</code>, <code>properties</code>: pointing to |
| 165 | the associated element in the tree, those may return None in case no such |
| 166 | link exists.</li> |
| 167 | </ul> |
| 168 | <p>Also note the need to explicitely deallocate documents with freeDoc() . |
| 169 | Reference counting for libxml2 trees would need quite a lot of work to |
| 170 | function properly, and rather than risk memory leaks if not implemented |
| 171 | correctly it sounds safer to have an explicit function to free a tree. The |
| 172 | wrapper python objects like doc, root or child are them automatically garbage |
| 173 | collected.</p> |
| 174 | <h3>validate.py:</h3> |
| 175 | <p>This test check the validation interfaces and redirection of error |
| 176 | messages:</p> |
| 177 | <pre>import libxml2 |
| 178 | |
| 179 | #desactivate error messages from the validation |
| 180 | def noerr(ctx, str): |
| 181 | pass |
| 182 | |
| 183 | libxml2.registerErrorHandler(noerr, None) |
| 184 | |
| 185 | ctxt = libxml2.createFileParserCtxt("invalid.xml") |
| 186 | ctxt.validate(1) |
| 187 | ctxt.parseDocument() |
| 188 | doc = ctxt.doc() |
| 189 | valid = ctxt.isValid() |
| 190 | doc.freeDoc() |
| 191 | if valid != 0: |
| 192 | print "validity chec failed"</pre> |
| 193 | <p>The first thing to notice is the call to registerErrorHandler(), it |
| 194 | defines a new error handler global to the library. It is used to avoid seeing |
| 195 | the error messages when trying to validate the invalid document.</p> |
| 196 | <p>The main interest of that test is the creation of a parser context with |
| 197 | createFileParserCtxt() and how the behaviour can be changed before calling |
| 198 | parseDocument() . Similary the informations resulting from the parsing phase |
| 199 | are also available using context methods.</p> |
| 200 | <p>Contexts like nodes are defined as class and the libxml2 wrappers maps the |
| 201 | C function interfaces in terms of objects method as much as possible. The |
| 202 | best to get a complete view of what methods are supported is to look at the |
| 203 | libxml2.py module containing all the wrappers.</p> |
| 204 | <h3>push.py:</h3> |
| 205 | <p>This test show how to activate the push parser interface:</p> |
| 206 | <pre>import libxml2 |
| 207 | |
| 208 | ctxt = libxml2.createPushParser(None, "<foo", 4, "test.xml") |
| 209 | ctxt.parseChunk("/>", 2, 1) |
| 210 | doc = ctxt.doc() |
| 211 | |
| 212 | doc.freeDoc()</pre> |
| 213 | <p>The context is created with a speciall call based on the |
| 214 | xmlCreatePushParser() from the C library. The first argument is an optional |
| 215 | SAX callback object, then the initial set of data, the lenght and the name of |
| 216 | the resource in case URI-References need to be computed by the parser.</p> |
| 217 | <p>Then the data are pushed using the parseChunk() method, the last call |
| 218 | setting the thrird argument terminate to 1.</p> |
| 219 | <h3>pushSAX.py:</h3> |
| 220 | <p>this test show the use of the event based parsing interfaces. In this case |
| 221 | the parser does not build a document, but provides callback information as |
| 222 | the parser makes progresses analyzing the data being provided:</p> |
| 223 | <pre>import libxml2 |
| 224 | log = "" |
| 225 | |
| 226 | class callback: |
| 227 | def startDocument(self): |
| 228 | global log |
| 229 | log = log + "startDocument:" |
| 230 | |
| 231 | def endDocument(self): |
| 232 | global log |
| 233 | log = log + "endDocument:" |
| 234 | |
| 235 | def startElement(self, tag, attrs): |
| 236 | global log |
| 237 | log = log + "startElement %s %s:" % (tag, attrs) |
| 238 | |
| 239 | def endElement(self, tag): |
| 240 | global log |
| 241 | log = log + "endElement %s:" % (tag) |
| 242 | |
| 243 | def characters(self, data): |
| 244 | global log |
| 245 | log = log + "characters: %s:" % (data) |
| 246 | |
| 247 | def warning(self, msg): |
| 248 | global log |
| 249 | log = log + "warning: %s:" % (msg) |
| 250 | |
| 251 | def error(self, msg): |
| 252 | global log |
| 253 | log = log + "error: %s:" % (msg) |
| 254 | |
| 255 | def fatalError(self, msg): |
| 256 | global log |
| 257 | log = log + "fatalError: %s:" % (msg) |
| 258 | |
| 259 | handler = callback() |
| 260 | |
| 261 | ctxt = libxml2.createPushParser(handler, "<foo", 4, "test.xml") |
| 262 | chunk = " url='tst'>b" |
| 263 | ctxt.parseChunk(chunk, len(chunk), 0) |
| 264 | chunk = "ar</foo>" |
| 265 | ctxt.parseChunk(chunk, len(chunk), 1) |
| 266 | |
| 267 | reference = "startDocument:startElement foo {'url': 'tst'}:characters: bar:endElement foo:endDocument:" |
| 268 | if log != reference: |
| 269 | print "Error got: %s" % log |
| 270 | print "Exprected: %s" % reference</pre> |
| 271 | <p>The key object in that test is the handler, it provides a number of entry |
| 272 | points which can be called by the parser as it makes progresses to indicate |
| 273 | the information set obtained. The full set of callback is larger than what |
| 274 | the callback class in that specific example implements (see the SAX |
| 275 | definition for a complete list). The wrapper will only call those supplied by |
| 276 | the object when activated. The startElement receives the names of the element |
| 277 | and a dictionnary containing the attributes carried by this element.</p> |
| 278 | <p>Also note that the reference string generated from the callback shows a |
| 279 | single character call even though the string "bar" is passed to the parser |
| 280 | from 2 different call to parseChunk()</p> |
| 281 | <h3>xpath.py:</h3> |
| 282 | <p>This is a basic test of XPath warppers support</p> |
| 283 | <pre>import libxml2 |
| 284 | |
| 285 | doc = libxml2.parseFile("tst.xml") |
| 286 | ctxt = doc.xpathNewContext() |
| 287 | res = ctxt.xpathEval("//*") |
| 288 | if len(res) != 2: |
| 289 | print "xpath query: wrong node set size" |
| 290 | sys.exit(1) |
| 291 | if res[0].name != "doc" or res[1].name != "foo": |
| 292 | print "xpath query: wrong node set value" |
| 293 | sys.exit(1) |
| 294 | doc.freeDoc() |
| 295 | ctxt.xpathFreeContext()</pre> |
| 296 | <p>This test parses a file, then create an XPath context to evaluate XPath |
| 297 | expression on it. The xpathEval() method execute an XPath query and returns |
| 298 | the result mapped in a Python way. String and numbers are natively converted, |
| 299 | and node sets are returned as a tuple of libxml2 Python nodes wrappers. Like |
| 300 | the document, the XPath context need to be freed explicitely, also not that |
| 301 | the result of the XPath query may point back to the document tree and hence |
| 302 | the document must be freed after the result of the query is used.</p> |
| 303 | <h3>xpathext.py:</h3> |
| 304 | <p>This test shows how to extend the XPath engine with functions written in |
| 305 | python:</p> |
| 306 | <pre>import libxml2 |
| 307 | |
| 308 | def foo(ctx, x): |
| 309 | return x + 1 |
| 310 | |
| 311 | doc = libxml2.parseFile("tst.xml") |
| 312 | ctxt = doc.xpathNewContext() |
| 313 | libxml2.registerXPathFunction(ctxt._o, "foo", None, foo) |
| 314 | res = ctxt.xpathEval("foo(1)") |
| 315 | if res != 2: |
| 316 | print "xpath extension failure" |
| 317 | doc.freeDoc() |
| 318 | ctxt.xpathFreeContext()</pre> |
| 319 | <p>Note how the extension function is registered with the context (but that |
| 320 | part is not yet finalized, ths may change slightly in the future).</p> |
| 321 | <h3>tstxpath.py:</h3> |
| 322 | <p>This test is similar to the previousone but shows how the extension |
| 323 | function can access the XPath evaluation context:</p> |
| 324 | <pre>def foo(ctx, x): |
| 325 | global called |
| 326 | |
| 327 | # |
| 328 | # test that access to the XPath evaluation contexts |
| 329 | # |
| 330 | pctxt = libxml2.xpathParserContext(_obj=ctx) |
| 331 | ctxt = pctxt.context() |
| 332 | called = ctxt.function() |
| 333 | return x + 1</pre> |
| 334 | <p>All the interfaces around the XPath parser(or rather evaluation) context |
| 335 | are not finalized, but it should be sufficient to do contextual work at the |
| 336 | evaluation point.</p> |
| 337 | <h3>Memory debugging:</h3> |
| 338 | <p>last but not least, all tests starts with the following prologue:</p> |
| 339 | <pre>#memory debug specific |
| 340 | libxml2.debugMemory(1) |
| 341 | </pre> |
| 342 | <p>and ends with the following epilogue:</p> |
| 343 | <pre>#memory debug specific |
| 344 | libxml2.cleanupParser() |
| 345 | if libxml2.debugMemory(1) == 0: |
| 346 | print "OK" |
| 347 | else: |
| 348 | print "Memory leak %d bytes" % (libxml2.debugMemory(1)) |
| 349 | libxml2.dumpMemory()</pre> |
| 350 | <p>Those activate the memory debugging interface of libxml2 where all |
| 351 | alloacted block in the library are tracked. The prologue then cleans up the |
| 352 | library state and checks that all allocated memory has been freed. If not it |
| 353 | calls dumpMemory() which saves that list in a <code>.memdump</code> file.</p> |
| 354 | <p><a href="bugs.html">Daniel Veillard</a></p> |
| 355 | </td></tr></table></td></tr></table></td></tr></table></td> |
| 356 | </tr></table></td></tr></table> |
| 357 | </body> |
| 358 | </html> |