2 :mod:`xml.sax.handler` --- Base classes for SAX handlers
3 ========================================================
5 .. module:: xml.sax.handler
6 :synopsis: Base classes for SAX event handlers.
7 .. moduleauthor:: Lars Marius Garshol <larsga@garshol.priv.no>
8 .. sectionauthor:: Martin v. Löwis <martin@v.loewis.de>
13 The SAX API defines four kinds of handlers: content handlers, DTD handlers,
14 error handlers, and entity resolvers. Applications normally only need to
15 implement those interfaces whose events they are interested in; they can
16 implement the interfaces in a single object or in multiple objects. Handler
17 implementations should inherit from the base classes provided in the module
18 :mod:`xml.sax.handler`, so that all methods get default implementations.
21 .. class:: ContentHandler
23 This is the main callback interface in SAX, and the one most important to
24 applications. The order of events in this interface mirrors the order of the
25 information in the document.
32 This interface specifies only those DTD events required for basic parsing
33 (unparsed entities and attributes).
36 .. class:: EntityResolver
38 Basic interface for resolving entities. If you create an object implementing
39 this interface, then register the object with your Parser, the parser will call
40 the method in your object to resolve all external entities.
43 .. class:: ErrorHandler
45 Interface used by the parser to present error and warning messages to the
46 application. The methods of this object control whether errors are immediately
47 converted to exceptions or are handled in some other way.
49 In addition to these classes, :mod:`xml.sax.handler` provides symbolic constants
50 for the feature and property names.
53 .. data:: feature_namespaces
55 Value: ``"http://xml.org/sax/features/namespaces"`` --- true: Perform Namespace
56 processing. --- false: Optionally do not perform Namespace processing (implies
57 namespace-prefixes; default). --- access: (parsing) read-only; (not parsing)
61 .. data:: feature_namespace_prefixes
63 Value: ``"http://xml.org/sax/features/namespace-prefixes"`` --- true: Report
64 the original prefixed names and attributes used for Namespace
65 declarations. --- false: Do not report attributes used for Namespace
66 declarations, and optionally do not report original prefixed names
67 (default). --- access: (parsing) read-only; (not parsing) read/write
70 .. data:: feature_string_interning
72 Value: ``"http://xml.org/sax/features/string-interning"`` --- true: All element
73 names, prefixes, attribute names, Namespace URIs, and local names are interned
74 using the built-in intern function. --- false: Names are not necessarily
75 interned, although they may be (default). --- access: (parsing) read-only; (not
79 .. data:: feature_validation
81 Value: ``"http://xml.org/sax/features/validation"`` --- true: Report all
82 validation errors (implies external-general-entities and
83 external-parameter-entities). --- false: Do not report validation errors. ---
84 access: (parsing) read-only; (not parsing) read/write
87 .. data:: feature_external_ges
89 Value: ``"http://xml.org/sax/features/external-general-entities"`` --- true:
90 Include all external general (text) entities. --- false: Do not include
91 external general entities. --- access: (parsing) read-only; (not parsing)
95 .. data:: feature_external_pes
97 Value: ``"http://xml.org/sax/features/external-parameter-entities"`` --- true:
98 Include all external parameter entities, including the external DTD subset. ---
99 false: Do not include any external parameter entities, even the external DTD
100 subset. --- access: (parsing) read-only; (not parsing) read/write
103 .. data:: all_features
105 List of all features.
108 .. data:: property_lexical_handler
110 Value: ``"http://xml.org/sax/properties/lexical-handler"`` --- data type:
111 xml.sax.sax2lib.LexicalHandler (not supported in Python 2) --- description: An
112 optional extension handler for lexical events like comments. --- access:
116 .. data:: property_declaration_handler
118 Value: ``"http://xml.org/sax/properties/declaration-handler"`` --- data type:
119 xml.sax.sax2lib.DeclHandler (not supported in Python 2) --- description: An
120 optional extension handler for DTD-related events other than notations and
121 unparsed entities. --- access: read/write
124 .. data:: property_dom_node
126 Value: ``"http://xml.org/sax/properties/dom-node"`` --- data type:
127 org.w3c.dom.Node (not supported in Python 2) --- description: When parsing,
128 the current DOM node being visited if this is a DOM iterator; when not parsing,
129 the root DOM node for iteration. --- access: (parsing) read-only; (not parsing)
133 .. data:: property_xml_string
135 Value: ``"http://xml.org/sax/properties/xml-string"`` --- data type: String ---
136 description: The literal string of characters that was the source for the
137 current event. --- access: read-only
140 .. data:: all_properties
142 List of all known property names.
145 .. _content-handler-objects:
147 ContentHandler Objects
148 ----------------------
150 Users are expected to subclass :class:`ContentHandler` to support their
151 application. The following methods are called by the parser on the appropriate
152 events in the input document:
155 .. method:: ContentHandler.setDocumentLocator(locator)
157 Called by the parser to give the application a locator for locating the origin
160 SAX parsers are strongly encouraged (though not absolutely required) to supply a
161 locator: if it does so, it must supply the locator to the application by
162 invoking this method before invoking any of the other methods in the
163 DocumentHandler interface.
165 The locator allows the application to determine the end position of any
166 document-related event, even if the parser is not reporting an error. Typically,
167 the application will use this information for reporting its own errors (such as
168 character content that does not match an application's business rules). The
169 information returned by the locator is probably not sufficient for use with a
172 Note that the locator will return correct information only during the invocation
173 of the events in this interface. The application should not attempt to use it at
177 .. method:: ContentHandler.startDocument()
179 Receive notification of the beginning of a document.
181 The SAX parser will invoke this method only once, before any other methods in
182 this interface or in DTDHandler (except for :meth:`setDocumentLocator`).
185 .. method:: ContentHandler.endDocument()
187 Receive notification of the end of a document.
189 The SAX parser will invoke this method only once, and it will be the last method
190 invoked during the parse. The parser shall not invoke this method until it has
191 either abandoned parsing (because of an unrecoverable error) or reached the end
195 .. method:: ContentHandler.startPrefixMapping(prefix, uri)
197 Begin the scope of a prefix-URI Namespace mapping.
199 The information from this event is not necessary for normal Namespace
200 processing: the SAX XML reader will automatically replace prefixes for element
201 and attribute names when the ``feature_namespaces`` feature is enabled (the
204 There are cases, however, when applications need to use prefixes in character
205 data or in attribute values, where they cannot safely be expanded automatically;
206 the :meth:`startPrefixMapping` and :meth:`endPrefixMapping` events supply the
207 information to the application to expand prefixes in those contexts itself, if
210 .. XXX This is not really the default, is it? MvL
212 Note that :meth:`startPrefixMapping` and :meth:`endPrefixMapping` events are not
213 guaranteed to be properly nested relative to each-other: all
214 :meth:`startPrefixMapping` events will occur before the corresponding
215 :meth:`startElement` event, and all :meth:`endPrefixMapping` events will occur
216 after the corresponding :meth:`endElement` event, but their order is not
220 .. method:: ContentHandler.endPrefixMapping(prefix)
222 End the scope of a prefix-URI mapping.
224 See :meth:`startPrefixMapping` for details. This event will always occur after
225 the corresponding :meth:`endElement` event, but the order of
226 :meth:`endPrefixMapping` events is not otherwise guaranteed.
229 .. method:: ContentHandler.startElement(name, attrs)
231 Signals the start of an element in non-namespace mode.
233 The *name* parameter contains the raw XML 1.0 name of the element type as a
234 string and the *attrs* parameter holds an object of the :class:`Attributes`
235 interface (see :ref:`attributes-objects`) containing the attributes of
236 the element. The object passed as *attrs* may be re-used by the parser; holding
237 on to a reference to it is not a reliable way to keep a copy of the attributes.
238 To keep a copy of the attributes, use the :meth:`copy` method of the *attrs*
242 .. method:: ContentHandler.endElement(name)
244 Signals the end of an element in non-namespace mode.
246 The *name* parameter contains the name of the element type, just as with the
247 :meth:`startElement` event.
250 .. method:: ContentHandler.startElementNS(name, qname, attrs)
252 Signals the start of an element in namespace mode.
254 The *name* parameter contains the name of the element type as a ``(uri,
255 localname)`` tuple, the *qname* parameter contains the raw XML 1.0 name used in
256 the source document, and the *attrs* parameter holds an instance of the
257 :class:`AttributesNS` interface (see :ref:`attributes-ns-objects`)
258 containing the attributes of the element. If no namespace is associated with
259 the element, the *uri* component of *name* will be ``None``. The object passed
260 as *attrs* may be re-used by the parser; holding on to a reference to it is not
261 a reliable way to keep a copy of the attributes. To keep a copy of the
262 attributes, use the :meth:`copy` method of the *attrs* object.
264 Parsers may set the *qname* parameter to ``None``, unless the
265 ``feature_namespace_prefixes`` feature is activated.
268 .. method:: ContentHandler.endElementNS(name, qname)
270 Signals the end of an element in namespace mode.
272 The *name* parameter contains the name of the element type, just as with the
273 :meth:`startElementNS` method, likewise the *qname* parameter.
276 .. method:: ContentHandler.characters(content)
278 Receive notification of character data.
280 The Parser will call this method to report each chunk of character data. SAX
281 parsers may return all contiguous character data in a single chunk, or they may
282 split it into several chunks; however, all of the characters in any single event
283 must come from the same external entity so that the Locator provides useful
286 *content* may be a Unicode string or a byte string; the ``expat`` reader module
287 produces always Unicode strings.
291 The earlier SAX 1 interface provided by the Python XML Special Interest Group
292 used a more Java-like interface for this method. Since most parsers used from
293 Python did not take advantage of the older interface, the simpler signature was
294 chosen to replace it. To convert old code to the new interface, use *content*
295 instead of slicing content with the old *offset* and *length* parameters.
298 .. method:: ContentHandler.ignorableWhitespace(whitespace)
300 Receive notification of ignorable whitespace in element content.
302 Validating Parsers must use this method to report each chunk of ignorable
303 whitespace (see the W3C XML 1.0 recommendation, section 2.10): non-validating
304 parsers may also use this method if they are capable of parsing and using
307 SAX parsers may return all contiguous whitespace in a single chunk, or they may
308 split it into several chunks; however, all of the characters in any single event
309 must come from the same external entity, so that the Locator provides useful
313 .. method:: ContentHandler.processingInstruction(target, data)
315 Receive notification of a processing instruction.
317 The Parser will invoke this method once for each processing instruction found:
318 note that processing instructions may occur before or after the main document
321 A SAX parser should never report an XML declaration (XML 1.0, section 2.8) or a
322 text declaration (XML 1.0, section 4.3.1) using this method.
325 .. method:: ContentHandler.skippedEntity(name)
327 Receive notification of a skipped entity.
329 The Parser will invoke this method once for each entity skipped. Non-validating
330 processors may skip entities if they have not seen the declarations (because,
331 for example, the entity was declared in an external DTD subset). All processors
332 may skip external entities, depending on the values of the
333 ``feature_external_ges`` and the ``feature_external_pes`` properties.
336 .. _dtd-handler-objects:
341 :class:`DTDHandler` instances provide the following methods:
344 .. method:: DTDHandler.notationDecl(name, publicId, systemId)
346 Handle a notation declaration event.
349 .. method:: DTDHandler.unparsedEntityDecl(name, publicId, systemId, ndata)
351 Handle an unparsed entity declaration event.
354 .. _entity-resolver-objects:
356 EntityResolver Objects
357 ----------------------
360 .. method:: EntityResolver.resolveEntity(publicId, systemId)
362 Resolve the system identifier of an entity and return either the system
363 identifier to read from as a string, or an InputSource to read from. The default
364 implementation returns *systemId*.
367 .. _sax-error-handler:
372 Objects with this interface are used to receive error and warning information
373 from the :class:`XMLReader`. If you create an object that implements this
374 interface, then register the object with your :class:`XMLReader`, the parser
375 will call the methods in your object to report all warnings and errors. There
376 are three levels of errors available: warnings, (possibly) recoverable errors,
377 and unrecoverable errors. All methods take a :exc:`SAXParseException` as the
378 only parameter. Errors and warnings may be converted to an exception by raising
379 the passed-in exception object.
382 .. method:: ErrorHandler.error(exception)
384 Called when the parser encounters a recoverable error. If this method does not
385 raise an exception, parsing may continue, but further document information
386 should not be expected by the application. Allowing the parser to continue may
387 allow additional errors to be discovered in the input document.
390 .. method:: ErrorHandler.fatalError(exception)
392 Called when the parser encounters an error it cannot recover from; parsing is
393 expected to terminate when this method returns.
396 .. method:: ErrorHandler.warning(exception)
398 Called when the parser presents minor warning information to the application.
399 Parsing is expected to continue when this method returns, and document
400 information will continue to be passed to the application. Raising an exception
401 in this method will cause parsing to end.