# HG changeset patch
# User paulb
# Date 1105842553 0
# Node ID 6ec740a93b52411de7ce82df8d15e3cdb04da298
# Parent  d03b350b9d4a39d9c7b95a52e81777e934dd445d
[project @ 2005-01-16 02:29:13 by paulb]
Added libxml2dom.macrolib package to the setup script.
Added documentation about importNode and the macro experiment.

diff -r d03b350b9d4a -r 6ec740a93b52 README.txt
--- a/README.txt	Sun Jan 16 02:02:42 2005 +0000
+++ b/README.txt	Sun Jan 16 02:29:13 2005 +0000
@@ -6,3 +6,17 @@
 Use of importNode seems to cause some kind of memory issue, probably related
 to nodes being shared across documents. This was observed in libxml2 2.6.0 but
 appears to be fixed in libxml2 2.6.16.
+
+Even compared to minidom, importNode is very slow (even the
+libxml2dom.macrolib implementation, too). A way is needed to get libxml2 to do
+the node copying itself.
+
+Experiments
+-----------
+
+The libxml2macro.py program, along with the libxml2dom.macrolib package
+provide support for writing DOM-style code which is then translated to
+libxml2-style code before being compiled to normal Python modules. This
+special translation should eliminate the need for high-level wrapper objects
+in many cases, since the actual compiled code will be manipulating the libxml2
+objects directly - the principal exception being that of attribute nodes.
diff -r d03b350b9d4a -r 6ec740a93b52 setup.py
--- a/setup.py	Sun Jan 16 02:02:42 2005 +0000
+++ b/setup.py	Sun Jan 16 02:29:13 2005 +0000
@@ -11,5 +11,5 @@
     author_email = "paul@boddie.org.uk",
     url          = "http://www.boddie.org.uk/python/libxml2dom.html",
     version      = libxml2dom.__version__,
-    packages     = ["libxml2dom"]
+    packages     = ["libxml2dom", "libxml2dom.macrolib"]
     )