<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
Currently, XML library loading in owslib is wrapped in owslib/etree.py [1], which sets the appropriate library according to what the wrapper finds for python XML libs via try/except with imports. Calling modules always see owslib.etree as a result.<br><br>The current behaviour of [1] is as follows:<br><br>- try to load elementtree.ElementTree and patch namespaces<br>- if that fails, try to load xml.etree.ElementTree and patch namespaces<br>- if that fails, try to load lxml.etree<br>- if that fails, raise error<br><br>I propose we reverse this order so that lxml.etree is looked for _first_, then xml.etree.ElementTree, then elementtree.ElementTree. This would ensure that lxml.etree would be loaded first to take advantage of features of lxml (which may not be in owslib, but the calling app[s] use/call), and elementtree.ElementTree would be called as the last resort.<br><br>The proposed patch is at http://pastebin.com/bEs4H00E for review and comment.<br><br>Any objections or comments?<br><br>Thanks<br><br>..Tom<br><br>[1] https://owslib.svn.sourceforge.net/svnroot/owslib/trunk/owslib/etree.py<br> </div></body>
</html>