Current File : //proc/thread-self/root/opt/alt/python34/lib64/python3.4/xml/sax/__pycache__/handler.cpython-34.pyc
�
j fb6 � @ s� d Z d Z Gd d � d � Z Gd d � d � Z Gd d � d � Z Gd d � d � Z d
Z d Z d Z d
Z d Z
d Z e e e e e
e g Z d Z
d Z d Z d Z d Z d Z e
e e e e e g Z d S)a0
This module contains the core classes of version 2.0 of SAX for Python.
This file provides only default classes with absolutely minimum
functionality, from which drivers and applications can be subclassed.
Many of these classes are empty and are included only as documentation
of the interfaces.
$Id$
z2.0betac @ s: e Z d Z d Z d d � Z d d � Z d d � Z d S) � ErrorHandlera� Basic interface for SAX error handlers.
If you create an object that implements this interface, then
register the object with your XMLReader, the parser will call the
methods in your object to report all warnings and errors. There
are three levels of errors available: warnings, (possibly)
recoverable errors, and unrecoverable errors. All methods take a
SAXParseException as the only parameter.c C s
| � d S)zHandle a recoverable error.N� )�self� exceptionr r �4/opt/alt/python34/lib64/python3.4/xml/sax/handler.py�error s zErrorHandler.errorc C s
| � d S)z Handle a non-recoverable error.Nr )r r r r r �
fatalError$ s zErrorHandler.fatalErrorc C s t | � d S)zHandle a warning.N)�print)r r r r r �warning( s zErrorHandler.warningN)�__name__�
__module__� __qualname__�__doc__r r r r r r r r s r c @ s� e Z d Z d Z d d � Z d d � Z d d � Z d d � Z d
d � Z d d
� Z d d � Z
d d � Z d d � Z d d � Z
d d � Z d d � Z d d � Z d d � Z d S) �ContentHandlerz�Interface for receiving logical document content events.
This is the main callback interface in SAX, and the one most
important to applications. The order of events in this interface
mirrors the order of the information in the document.c C s
d | _ d S)N)�_locator)r r r r �__init__6 s zContentHandler.__init__c C s
| | _ d S)a# Called by the parser to give the application a locator for
locating the origin of document events.
SAX parsers are strongly encouraged (though not absolutely
required) to supply a locator: if it does so, it must supply
the locator to the application by invoking this method before
invoking any of the other methods in the DocumentHandler
interface.
The locator allows the application to determine the end
position of any document-related event, even if the parser is
not reporting an error. Typically, the application will use
this information for reporting its own errors (such as
character content that does not match an application's
business rules). The information returned by the locator is
probably not sufficient for use with a search engine.
Note that the locator will return correct information only
during the invocation of the events in this interface. The
application should not attempt to use it at any other time.N)r )r Zlocatorr r r �setDocumentLocator9 s z!ContentHandler.setDocumentLocatorc C s d S)z�Receive notification of the beginning of a document.
The SAX parser will invoke this method only once, before any
other methods in this interface or in DTDHandler (except for
setDocumentLocator).Nr )r r r r �
startDocumentP s z ContentHandler.startDocumentc C s d S)aQ Receive notification of the end of a document.
The SAX parser will invoke this method only once, and it will
be the last method invoked during the parse. The parser shall
not invoke this method until it has either abandoned parsing
(because of an unrecoverable error) or reached the end of
input.Nr )r r r r � endDocumentW s zContentHandler.endDocumentc C s d S)a Begin the scope of a prefix-URI Namespace mapping.
The information from this event is not necessary for normal
Namespace processing: the SAX XML reader will automatically
replace prefixes for element and attribute names when the
http://xml.org/sax/features/namespaces feature is true (the
default).
There are cases, however, when applications need to use
prefixes in character data or in attribute values, where they
cannot safely be expanded automatically; the
start/endPrefixMapping event supplies the information to the
application to expand prefixes in those contexts itself, if
necessary.
Note that start/endPrefixMapping events are not guaranteed to
be properly nested relative to each-other: all
startPrefixMapping events will occur before the corresponding
startElement event, and all endPrefixMapping events will occur
after the corresponding endElement event, but their order is
not guaranteed.Nr )r �prefixZurir r r �startPrefixMapping` s z!ContentHandler.startPrefixMappingc C s d S)z�End the scope of a prefix-URI mapping.
See startPrefixMapping for details. This event will always
occur after the corresponding endElement event, but the order
of endPrefixMapping events is not otherwise guaranteed.Nr )r r r r r �endPrefixMappingw s z ContentHandler.endPrefixMappingc C s d S)a Signals the start of an element in non-namespace mode.
The name parameter contains the raw XML 1.0 name of the
element type as a string and the attrs parameter holds an
instance of the Attributes class containing the attributes of
the element.Nr )r �name�attrsr r r � startElement~ s zContentHandler.startElementc C s d S)z�Signals the end of an element in non-namespace mode.
The name parameter contains the name of the element type, just
as with the startElement event.Nr )r r r r r �
endElement� s zContentHandler.endElementc C s d S)a� Signals the start of an element in namespace mode.
The name parameter contains the name of the element type as a
(uri, localname) tuple, the qname parameter the raw XML 1.0
name used in the source document, and the attrs parameter
holds an instance of the Attributes class containing the
attributes of the element.
The uri part of the name tuple is None for elements which have
no namespace.Nr )r r �qnamer r r r �startElementNS� s z ContentHandler.startElementNSc C s d S)z�Signals the end of an element in namespace mode.
The name parameter contains the name of the element type, just
as with the startElementNS event.Nr )r r r r r r � endElementNS� s zContentHandler.endElementNSc C s d S)a� Receive notification of character data.
The Parser will call this method to report each chunk of
character data. SAX parsers may return all contiguous
character data in a single chunk, or they may split it into
several chunks; however, all of the characters in any single
event must come from the same external entity so that the
Locator provides useful information.Nr )r Zcontentr r r �
characters� s zContentHandler.charactersc C s d S)aw Receive notification of ignorable whitespace in element content.
Validating Parsers must use this method to report each chunk
of ignorable whitespace (see the W3C XML 1.0 recommendation,
section 2.10): non-validating parsers may also use this method
if they are capable of parsing and using content models.
SAX parsers may return all contiguous whitespace in a single
chunk, or they may split it into several chunks; however, all
of the characters in any single event must come from the same
external entity, so that the Locator provides useful
information.Nr )r Z
whitespacer r r �ignorableWhitespace� s z"ContentHandler.ignorableWhitespacec C s d S)a� Receive notification of a processing instruction.
The Parser will invoke this method once for each processing
instruction found: note that processing instructions may occur
before or after the main document element.
A SAX parser should never report an XML declaration (XML 1.0,
section 2.8) or a text declaration (XML 1.0, section 4.3.1)
using this method.Nr )r �target�datar r r �processingInstruction� s z$ContentHandler.processingInstructionc C s d S)a Receive notification of a skipped entity.
The Parser will invoke this method once for each entity
skipped. Non-validating processors may skip entities if they
have not seen the declarations (because, for example, the
entity was declared in an external DTD subset). All processors
may skip external entities, depending on the values of the
http://xml.org/sax/features/external-general-entities and the
http://xml.org/sax/features/external-parameter-entities
properties.Nr )r r r r r �
skippedEntity� s z ContentHandler.skippedEntityN)r
r r r
r r r r r r r r r r r r r" r# r r r r r / s
r c @ s. e Z d Z d Z d d � Z d d � Z d S)�
DTDHandlerz�Handle DTD events.
This interface specifies only those DTD events required for basic
parsing (unparsed entities and attributes).c C s d S)z$Handle a notation declaration event.Nr )r r �publicId�systemIdr r r � notationDecl� s zDTDHandler.notationDeclc C s d S)z,Handle an unparsed entity declaration event.Nr )r r r% r& Zndatar r r �unparsedEntityDecl� s z DTDHandler.unparsedEntityDeclN)r
r r r
r' r( r r r r r$ � s r$ c @ s" e Z d Z d Z d d � Z d S)�EntityResolvera7 Basic interface for resolving entities. If you create an object
implementing this interface, then register the object with your
Parser, the parser will call the method in your object to
resolve all external entities. Note that DefaultHandler implements
this interface with the default behaviour.c C s | S)z�Resolve the system identifier of an entity and return either
the system identifier to read from as a string, or an InputSource
to read from.r )r r% r& r r r �
resolveEntity� s z EntityResolver.resolveEntityN)r
r r r
r* r r r r r) � s r) z&http://xml.org/sax/features/namespacesz.http://xml.org/sax/features/namespace-prefixesz,http://xml.org/sax/features/string-interningz&http://xml.org/sax/features/validationz5http://xml.org/sax/features/external-general-entitiesz7http://xml.org/sax/features/external-parameter-entitiesz-http://xml.org/sax/properties/lexical-handlerz1http://xml.org/sax/properties/declaration-handlerz&http://xml.org/sax/properties/dom-nodez(http://xml.org/sax/properties/xml-stringz-http://www.python.org/sax/properties/encodingz3http://www.python.org/sax/properties/interning-dictN)r
�versionr r r$ r) Zfeature_namespacesZfeature_namespace_prefixesZfeature_string_interningZfeature_validationZfeature_external_gesZfeature_external_pesZ all_featuresZproperty_lexical_handlerZ property_declaration_handlerZproperty_dom_nodeZproperty_xml_stringZproperty_encodingZproperty_interning_dictZall_propertiesr r r r �<module>
s:
�
Mini Shell