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 and docs/LICENCE.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. Note
35 that such tests are retained for historical purposes and/or curiosity since
36 libxml2macro.py is no longer supported.
37
38 Issues
39 ------
40
41 Use of importNode seems to cause some kind of memory issue, probably related
42 to nodes being shared across documents. This was observed in libxml2 2.6.0 but
43 appears to be fixed in libxml2 2.6.16.
44
45 Even compared to minidom, importNode may seem very slow (even the
46 libxml2dom.macrolib implementation, too). A way is needed to get libxml2 to do
47 the node copying itself.
48
49 New in libxml2dom 0.3.1 (Changes since libxml2dom 0.3)
50 ------------------------------------------------------
51
52 * Fixed empty namespace declarations on elements created with namespaceURI
53 set to None. Previously, such declarations were missing.
54
55 New in libxml2dom 0.3 (Changes since libxml2dom 0.2.4)
56 ------------------------------------------------------
57
58 * Imposed much stricter tests on strings used with the libxml2dom API.
59 Strings given as arguments to methods and functions must now only contain
60 ASCII characters; any other character data must be provided as Unicode
61 objects. This change fixes various issues with XPath expressions, and
62 quite probably various other things.
63 * Fixed parentNode on Document objects (which caused xml.dom.ext.PrettyPrint
64 to crash).
65 * Added some support for the doctype attribute and related information.
66 * libxml2dom is now licensed under the LGPL - see docs/COPYING.txt for
67 details.
68
69 New in libxml2dom 0.2.4 (Changes since libxml2dom 0.2.3)
70 --------------------------------------------------------
71
72 * Fixed Unicode conversions in the Node's xpath method.
73
74 New in libxml2dom 0.2.3 (Changes since libxml2dom 0.2.2)
75 --------------------------------------------------------
76
77 * Fixed the parse function's docstring.
78 * Added the owner element to obtained attribute nodes.
79 * Fixed Debian package changelog distribution identifiers.
80
81 New in libxml2dom 0.2.2 (Changes since libxml2dom 0.2.1)
82 --------------------------------------------------------
83
84 * Fixed exception raising in parseURI, adding a docstring to explain the
85 current limitations around HTML parsing.
86
87 New in libxml2dom 0.2.1 (Changes since libxml2dom 0.2)
88 ------------------------------------------------------
89
90 * Moved libxml2macro script to the tools directory.
91 * Added getElementsByTagNameNS.
92 * Added a normalize implementation.
93 * Added HTML parsing support.
94 * Added prettyprinting support.
95 * Fixed parseURI.
96 * Introduced better testing for Unicode objects, especially since things
97 like rdflib like to subclass the unicode type, and it might be more
98 convenient to detect such subclasses and convert their values
99 automatically.
100 * Improved some of the API documentation.
101 * Introduced better suppression of warnings, network access, and other
102 potentially intrusive libxml2 features.
103 * Reorganised the documentation, expanding the README.txt file at the
104 expense of the HTML documentation, but removing older, less relevant
105 information.
106 * Added Debian package support.
107
108 New in libxml2dom 0.2 (Changes since libxml2dom 0.1.3)
109 ------------------------------------------------------
110
111 * Adopted libxml2macro code within the libxml2dom classes, removing any
112 dependencies on the libxml2 module - this makes everything much faster
113 and virtually removes any necessity to use libxml2macro.
114 * Improved attribute and document node handling.
115 * Introduced document reference management.
116 * Introduced NodeList wrapper objects.
117
118 New in libxml2dom 0.1.3 (Changes since libxml2dom 0.1.2)
119 --------------------------------------------------------
120
121 * Fixed createElement.
122 * Introduced experimental libxml2macro tools, tests and libraries.
123
124 New in libxml2dom 0.1.2 (Changes since libxml2dom 0.1.1)
125 --------------------------------------------------------
126
127 * Fixed getAttributeNode and getAttributeNodeNS.
128 * Added comment node creation.
129 * Fixed empty namespace usage with elements and attributes.
130 * Introduced usage of the libxml2 file and memory parsing features.
131 * Introduced suppression of DTD retrieval and validation as the default
132 behaviour.
133 * Added experimental XPath method support.
134
135 New in libxml2dom 0.1.1
136 -----------------------
137
138 * Fixed text node creation.
139 * Fixed setAttributeNS.
140 * Added encoding parameters to convenience methods.
141 * Added the missing previousSibling property.
142 * Added release number to the package.
143
144 Release Procedures
145 ------------------
146
147 Update the libxml2dom/__init__.py and libxml2dom/macrolib/__init__.py
148 __version__ attributes.
149 Change the version number and package filename/directory in the documentation.
150 Change code examples in the documentation if appropriate.
151 Update the release notes (see above).
152 Update the package release notes (in the packages directory).
153 Check the setup.py file and ensure that all package directories are mentioned.
154 Check the release information in the PKG-INFO file and in the package
155 changelog (and other files).
156 Tag, export.
157 Archive, upload.
158 Make packages (see below).
159 Update PyPI, PythonInfo Wiki, Vaults of Parnassus entries.
160
161 Making Packages
162 ---------------
163
164 To make Debian-based packages:
165
166 1. Create new package directories under packages if necessary.
167 2. Make a symbolic link in the distribution's root directory to keep the
168 Debian tools happy:
169
170 ln -s packages/ubuntu-hoary/python2.4-libxml2dom/debian/
171
172 3. Run the package builder:
173
174 dpkg-buildpackage -rfakeroot
175
176 4. Locate and tidy up the packages in the parent directory of the
177 distribution's root directory.