1 See docs/index.html for the libxml2dom documentation.
2
3 Issues
4 ------
5
6 Use of importNode seems to cause some kind of memory issue, probably related
7 to nodes being shared across documents. This was observed in libxml2 2.6.0 but
8 appears to be fixed in libxml2 2.6.16.
9
10 Even compared to minidom, importNode is very slow (even the
11 libxml2dom.macrolib implementation, too). A way is needed to get libxml2 to do
12 the node copying itself.
13
14 Experiments
15 -----------
16
17 The libxml2macro.py program, along with the libxml2dom.macrolib package
18 provide support for writing DOM-style code which is then translated to
19 libxml2-style code before being compiled to normal Python modules. This
20 special translation should eliminate the need for high-level wrapper objects
21 in many cases, since the actual compiled code will be manipulating the libxml2
22 objects directly - the principal exception being that of attribute nodes.