/
main.txt
277 lines (197 loc) · 9.3 KB
/
main.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
lxml
====
.. meta::
:description: lxml - the most feature-rich and easy-to-use library for processing XML and HTML in the Python language
:keywords: Python XML, XML processing, HTML, lxml, simple XML, ElementTree, etree, lxml.etree, objectify, XML parsing, XML validation, XPath, XSLT
.. class:: pagequote
| `» lxml takes all the pain out of XML. « <http://thread.gmane.org/gmane.comp.python.lxml.devel/3252/focus=3258>`_
| Stephan Richter
.. class:: eyecatcher
lxml is the most feature-rich
and easy-to-use library
for processing XML and HTML
in the Python language.
..
1 Introduction
2 Documentation
3 Download
4 Mailing list
5 Bug tracker
6 License
7 Old Versions
Introduction
------------
The lxml XML toolkit is a Pythonic binding for the C libraries
libxml2_ and libxslt_. It is unique in that it combines the speed and
XML feature completeness of these libraries with the simplicity of a
native Python API, mostly compatible but superior to the well-known
ElementTree_ API. The latest release works with all CPython versions
from 2.6 to 3.5. See the introduction_ for more information about
background and goals of the lxml project. Some common questions are
answered in the FAQ_.
.. _libxml2: http://xmlsoft.org/
.. _libxslt: http://xmlsoft.org/XSLT/
.. _introduction: intro.html
.. _FAQ: FAQ.html
Documentation
-------------
The complete lxml documentation is available for download as `PDF
documentation`_. The HTML documentation from this web site is part of
the normal `source download <#download>`_.
* Tutorials:
* the `lxml.etree tutorial for XML processing`_
* John Shipman's tutorial on `Python XML processing with lxml`_
* Fredrik Lundh's `tutorial for ElementTree`_
* ElementTree:
* `ElementTree API`_
* compatibility_ and differences of lxml.etree
* `ElementTree performance`_ characteristics and comparison
* lxml.etree:
* `lxml.etree specific API`_ documentation
* the `generated API documentation`_ as a reference
* parsing_ and validating_ XML
* `XPath and XSLT`_ support
* Python `XPath extension functions`_ for XPath and XSLT
* `custom XML element classes`_ for custom XML APIs (see `EuroPython 2008 talk`_)
* a `SAX compliant API`_ for interfacing with other XML tools
* a `C-level API`_ for interfacing with external C/Cython modules
* lxml.objectify:
* `lxml.objectify`_ API documentation
* a brief comparison of `objectify and etree`_
lxml.etree follows the ElementTree_ API as much as possible, building
it on top of the native libxml2 tree. If you are new to ElementTree,
start with the `lxml.etree tutorial for XML processing`_. See also the
ElementTree compatibility_ overview and the `ElementTree performance`_
page comparing lxml to the original ElementTree_ and cElementTree_
implementations.
Right after the `lxml.etree tutorial for XML processing`_ and the
ElementTree_ documentation, the next place to look is the `lxml.etree
specific API`_ documentation. It describes how lxml extends the
ElementTree API to expose libxml2 and libxslt specific XML
functionality, such as XPath_, `Relax NG`_, `XML Schema`_, XSLT_, and
`c14n`_. Python code can be called from XPath expressions and XSLT
stylesheets through the use of `XPath extension functions`_. lxml
also offers a `SAX compliant API`_, that works with the SAX support in
the standard library.
There is a separate module `lxml.objectify`_ that implements a data-binding
API on top of lxml.etree. See the `objectify and etree`_ FAQ entry for a
comparison.
In addition to the ElementTree API, lxml also features a sophisticated
API for `custom XML element classes`_. This is a simple way to write
arbitrary XML driven APIs on top of lxml. lxml.etree also has a
`C-level API`_ that can be used to efficiently extend lxml.etree in
external C modules, including fast custom element class support.
.. _ElementTree: http://effbot.org/zone/element-index.htm
.. _`ElementTree API`: http://effbot.org/zone/element-index.htm#documentation
.. _cElementTree: http://effbot.org/zone/celementtree.htm
.. _`tutorial for ElementTree`: http://effbot.org/zone/element.htm
.. _`lxml.etree tutorial for XML processing`: tutorial.html
.. _`Python XML processing with lxml`: http://www.nmt.edu/tcc/help/pubs/pylxml/
.. _`generated API documentation`: api/index.html
.. _`ElementTree performance`: performance.html
.. _`compatibility`: compatibility.html
.. _`lxml.etree specific API`: api.html
.. _`parsing`: parsing.html
.. _`validating`: validation.html
.. _`XPath and XSLT`: xpathxslt.html
.. _`XPath extension functions`: extensions.html
.. _`custom XML element classes`: element_classes.html
.. _`SAX compliant API`: sax.html
.. _`C-level API`: capi.html
.. _`lxml.objectify`: objectify.html
.. _`objectify and etree`: FAQ.html#what-is-the-difference-between-lxml-etree-and-lxml-objectify
.. _`EuroPython 2008 talk`: s5/lxml-ep2008.html
.. _XPath: http://www.w3.org/TR/xpath/
.. _`Relax NG`: http://www.relaxng.org/
.. _`XML Schema`: http://www.w3.org/XML/Schema
.. _`XSLT`: http://www.w3.org/TR/xslt
.. _`c14n`: http://www.w3.org/TR/xml-c14n
Download
--------
The best way to download lxml is to visit `lxml at the Python Package
Index <http://pypi.python.org/pypi/lxml/>`_ (PyPI). It has the source
that compiles on various platforms. The source distribution is signed
with `this key <pubkey.asc>`_.
The latest version is `lxml 3.5.0`_, released 2015-11-13
(`changes for 3.5.0`_). `Older versions <#old-versions>`_
are listed below.
Please take a look at the
`installation instructions <installation.html>`_ !
This complete web site (including the generated API documentation) is
part of the source distribution, so if you want to download the
documentation for offline use, take the source archive and copy the
``doc/html`` directory out of the source tree, or use the
`PDF documentation`_.
The latest installable developer sources should usually be available from the
`build server <http://lxml.de/build/>`_. It's also possible to check out
the latest development version of lxml from github directly, using a command
like this (assuming you use hg and have hg-git installed)::
hg clone git://github.com/lxml/lxml.git lxml
Alternatively, if you use git, this should work as well::
git clone git://github.com/lxml/lxml.git lxml
You can browse the `source repository`_ and its history through
the web. Please read `how to build lxml from source <build.html>`_
first. The `latest CHANGES`_ of the developer version are also
accessible. You can check there if a bug you found has been fixed
or a feature you want has been implemented in the latest trunk version.
.. _`source repository`: https://github.com/lxml/lxml/
.. _`latest CHANGES`: https://github.com/lxml/lxml/blob/master/CHANGES.txt
Mailing list
------------
Questions? Suggestions? Code to contribute? We have a `mailing list`_.
You can search the archive with Gmane_ or Google_.
.. _`mailing list`: http://lxml.de/mailinglist/
.. _Gmane: http://blog.gmane.org/gmane.comp.python.lxml.devel
.. _Google: http://www.google.com/webhp?q=site:comments.gmane.org%2Fgmane.comp.python.lxml.devel+
Bug tracker
-----------
lxml uses the `launchpad bug tracker`_. If you are sure you found a
bug in lxml, please file a bug report there. If you are not sure
whether some unexpected behaviour of lxml is a bug or not, please
check the documentation and ask on the `mailing list`_ first. Do not
forget to search the archive (e.g. with Gmane_)!
.. _`launchpad bug tracker`: https://launchpad.net/lxml/
License
-------
The lxml library is shipped under a `BSD license`_. libxml2 and libxslt2
itself are shipped under the `MIT license`_. There should therefore be no
obstacle to using lxml in your codebase.
.. _`BSD license`: https://github.com/lxml/lxml/blob/master/doc/licenses/BSD.txt
.. _`MIT license`: http://www.opensource.org/licenses/mit-license.html
Old Versions
------------
See the web sites of lxml
`1.3 <http://lxml.de/1.3/>`_,
`2.0 <http://lxml.de/2.0/>`_,
`2.1 <http://lxml.de/2.1/>`_,
`2.2 <http://lxml.de/2.2/>`_,
`2.3 <http://lxml.de/2.3/>`_,
`3.0 <http://lxml.de/3.0/>`_,
`3.1 <http://lxml.de/3.1/>`_,
`3.2 <http://lxml.de/3.2/>`_,
`3.3 <http://lxml.de/3.3/>`_
`3.4 <http://lxml.de/3.4/>`_
and the `latest in-development version <http://lxml.de/dev/>`_.
.. _`PDF documentation`: lxmldoc-3.5.0.pdf
* `lxml 3.5.0`_, released 2015-11-13 (`changes for 3.5.0`_)
* `lxml 3.5.0b1`_, released 2015-09-18 (`changes for 3.5.0b1`_)
* `lxml 3.4.4`_, released 2015-04-25 (`changes for 3.4.4`_)
* `lxml 3.4.3`_, released 2015-04-15 (`changes for 3.4.3`_)
* `lxml 3.4.2`_, released 2015-02-07 (`changes for 3.4.2`_)
* `lxml 3.4.1`_, released 2014-11-20 (`changes for 3.4.1`_)
* `lxml 3.4.0`_, released 2014-09-10 (`changes for 3.4.0`_)
* `older releases <http://lxml.de/3.4/#old-versions>`_
.. _`lxml 3.5.0`: /files/lxml-3.5.0.tgz
.. _`lxml 3.5.0b1`: /files/lxml-3.5.0b1.tgz
.. _`lxml 3.4.4`: /files/lxml-3.4.4.tgz
.. _`lxml 3.4.3`: /files/lxml-3.4.3.tgz
.. _`lxml 3.4.2`: /files/lxml-3.4.2.tgz
.. _`lxml 3.4.1`: /files/lxml-3.4.1.tgz
.. _`lxml 3.4.0`: /files/lxml-3.4.0.tgz
.. _`changes for 3.5.0`: /changes-3.5.0.html
.. _`changes for 3.5.0b1`: /changes-3.5.0b1.html
.. _`changes for 3.4.4`: /changes-3.4.4.html
.. _`changes for 3.4.3`: /changes-3.4.3.html
.. _`changes for 3.4.2`: /changes-3.4.2.html
.. _`changes for 3.4.1`: /changes-3.4.1.html
.. _`changes for 3.4.0`: /changes-3.4.0.html