1 Introduction
2 ------------
3
4 See docs/index.html for the libxml2dom documentation.
5
6 Contact, Copyright and Licence Information
7 ------------------------------------------
8
9 The current Web page for libxml2dom at the time of release is:
10
11 http://www.boddie.org.uk/python/libxml2dom.html
12
13 Copyright and licence information can be found in the docs directory - see
14 docs/COPYING.txt for more information.
15
16 Dependencies
17 ------------
18
19 libxml2 Tested with libxml2 2.6.17.
20 Use --with-python=<path to python executable> if building from
21 source. Previous releases of libxml2 in the 2.6 series may work,
22 but releases before 2.6.16 are not recommended.
23 Python Tested with Python 2.4.
24 Python releases from 2.2 onwards should be compatible with
25 libxml2dom. The principal requirement from such releases is the
26 new-style class support which permits the use of properties in
27 the libxml2dom implementation.
28
29 Testing
30 -------
31
32 Some of the tests require libxml2macro.py to be run on the test source code
33 first. Read the docstrings for the various test files before attempting to run
34 any of them. See also docs/NOTES_libxml2macro.txt for more information.
35
36 Issues
37 ------
38
39 Use of importNode seems to cause some kind of memory issue, probably related
40 to nodes being shared across documents. This was observed in libxml2 2.6.0 but
41 appears to be fixed in libxml2 2.6.16.
42
43 Even compared to minidom, importNode may seem very slow (even the
44 libxml2dom.macrolib implementation, too). A way is needed to get libxml2 to do
45 the node copying itself.
46
47 New in libxml2dom 0.2.1 (Changes since libxml2dom 0.2)
48 ------------------------------------------------------
49
50 * Moved libxml2macro script to the tools directory.
51 * Added getElementsByTagNameNS.
52 * Added HTML parsing support.
53 * Improved some of the API documentation.
54
55 New in libxml2dom 0.2 (Changes since libxml2dom 0.1.3)
56 ------------------------------------------------------
57
58 * Adopted libxml2macro code within the libxml2dom classes, removing any
59 dependencies on the libxml2 module - this makes everything much faster
60 and virtually removes any necessity to use libxml2macro.
61 * Improved attribute and document node handling.
62 * Introduced document reference management.
63 * Introduced NodeList wrapper objects.
64
65 New in libxml2dom 0.1.3 (Changes since libxml2dom 0.1.2)
66 --------------------------------------------------------
67
68 * Fixed createElement.
69 * Introduced experimental libxml2macro tools, tests and libraries.
70
71 New in libxml2dom 0.1.2 (Changes since libxml2dom 0.1.1)
72 --------------------------------------------------------
73
74 * Fixed getAttributeNode and getAttributeNodeNS.
75 * Added comment node creation.
76 * Fixed empty namespace usage with elements and attributes.
77 * Introduced usage of the libxml2 file and memory parsing features.
78 * Introduced suppression of DTD retrieval and validation as the default
79 behaviour.
80 * Added experimental XPath method support.
81
82 New in libxml2dom 0.1.1
83 -----------------------
84
85 * Fixed text node creation.
86 * Fixed setAttributeNS.
87 * Added encoding parameters to convenience methods.
88 * Added the missing previousSibling property.
89 * Added release number to the package.
90
91 Release Procedures
92 ------------------
93
94 Update the libxml2dom/__init__.py and libxml2dom/macrolib/__init__.py
95 __version__ attributes.
96 Change the version number and package filename/directory in the documentation.
97 Change code examples in the documentation if appropriate.
98 Update the release notes (see above).
99 Update the package release notes (in the packages directory).
100 Check the setup.py file and ensure that all package directories are mentioned.
101 Tag, export.
102 Archive, upload.
103 Make packages (see below).
104 Update PyPI, PythonInfo Wiki, Vaults of Parnassus entries.
105
106 Making Packages
107 ---------------
108
109 To make Debian packages:
110
111 1. Create new package directories under packages/debian if necessary.
112 2. Make a symbolic link in the distribution's root directory to keep the
113 Debian tools happy:
114
115 ln -s packages/debian/python2.4-libxml2dom/debian/
116
117 3. Run the package builder:
118
119 dpkg-buildpackage -rfakeroot
120
121 4. Locate and tidy up the packages in the parent directory of the
122 distribution's root directory.