⚝
One Hat Cyber Team
⚝
Your IP:
216.73.216.144
Server IP:
157.245.143.252
Server:
Linux www 6.11.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Oct 14 13:19:59 UTC 2024 x86_64
Server Software:
nginx/1.26.0
PHP Version:
8.3.11
Buat File
|
Buat Folder
Eksekusi
Dir :
~
/
lib
/
python3.12
/
xml
/
sax
/
__pycache__
/
View File Name :
handler.cpython-312.pyc
CRh= d Z dZ G d d Z G d d Z G d d Z G d d Zd Zd Zd Zd Z dZ dZ eeee e e gZ dZ dZdZdZdZdZe eeeeegZ G d d Zy)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 " e Zd ZdZd Zd Zd Zy) 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 |)zHandle a recoverable error. self exceptions &/usr/lib/python3.12/xml/sax/handler.pyerrorzErrorHandler.error c |)z Handle a non-recoverable error.r r s r fatalErrorzErrorHandler.fatalError$ r r c t | y)zHandle a warning.N)printr s r warningzErrorHandler.warning( s ir N)__name__ __module__ __qualname____doc__r r r r r r r r s 0r r c d e Zd ZdZd Zd Zd Zd Zd Zd Z d Z d Z d Z d Z d Zd Zd Zd Zy)ContentHandlerzInterface 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 d | _ y )N_locatorr s r __init__zContentHandler.__init__6 s r c || _ y)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.Nr )r locators r setDocumentLocatorz!ContentHandler.setDocumentLocator9 s * r c y)zReceive 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 s r startDocumentz ContentHandler.startDocumentP r c y)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 s r endDocumentzContentHandler.endDocumentW r" r c y)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 prefixuris r startPrefixMappingz!ContentHandler.startPrefixMapping` r" r c y)zEnd 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& s r endPrefixMappingz ContentHandler.endPrefixMappingw r" r c y)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 nameattrss r startElementzContentHandler.startElement~ r" r c y)zSignals 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, s r endElementzContentHandler.endElement r" r c y)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- s r startElementNSz ContentHandler.startElementNS r" r c y)zSignals 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, r3 s r endElementNSzContentHandler.endElementNS r" r c y)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 contents r characterszContentHandler.characters r" r c y)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 whitespaces r ignorableWhitespacez"ContentHandler.ignorableWhitespace r" r c y)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 targetdatas r processingInstructionz$ContentHandler.processingInstruction r" r c y)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 r0 s r skippedEntityz ContentHandler.skippedEntity r" r N)r r r r r r r! r$ r( r* r. r1 r4 r6 r: r= rA rC r r r r r / sN = . .C+ - 0 r r c e Zd ZdZd Zd Zy) DTDHandlerzHandle DTD events. This interface specifies only those DTD events required for basic parsing (unparsed entities and attributes).c y)z$Handle a notation declaration event.Nr )r r, publicIdsystemIds r notationDeclzDTDHandler.notationDecl r" r c y)z,Handle an unparsed entity declaration event.Nr )r r, rG rH ndatas r unparsedEntityDeclz DTDHandler.unparsedEntityDecl r" r N)r r r r rI rL r r r rE rE s 3 /7r rE c e Zd ZdZd Zy)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 |S )zResolve 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 rG rH s r resolveEntityz EntityResolver.resolveEntity s r N)r r r r rP r r r rN rN s 2 r rN 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-dictc . e Zd ZdZd Zd Zd Zd Zd Zy)LexicalHandlera Optional SAX2 handler for lexical events. This handler is used to obtain lexical information about an XML document, that is, information about how the document was encoded (as opposed to what it contains, which is reported to the ContentHandler), such as comments and CDATA marked section boundaries. To set the LexicalHandler of an XMLReader, use the setProperty method with the property identifier 'http://xml.org/sax/properties/lexical-handler'.c y)zReports a comment anywhere in the document (including the DTD and outside the document element). content is a string that holds the contents of the comment.Nr r8 s r commentzLexicalHandler.commentf r" r c y)a Report the start of the DTD declarations, if the document has an associated DTD. A startEntity event will be reported before declaration events from the external DTD subset are reported, and this can be used to infer from which subset DTD declarations derive. name is the name of the document element type, public_id the public identifier of the DTD (or None if none were supplied) and system_id the system identfier of the external subset (or None if none were supplied).Nr )r r, public_id system_ids r startDTDzLexicalHandler.startDTDl r" r c y)z$Signals the end of DTD declarations.Nr r s r endDTDzLexicalHandler.endDTDy r" r c y)zReports the beginning of a CDATA marked section. The contents of the CDATA marked section will be reported through the characters event.Nr r s r startCDATAzLexicalHandler.startCDATA| r" r c y)z*Reports the end of a CDATA marked section.Nr r s r endCDATAzLexicalHandler.endCDATA r" r N) r r r r rT rX rZ r\ r^ r r r rR rR Y s! 8G (3) 9r rR N)r versionr r rE rN feature_namespacesfeature_namespace_prefixesfeature_string_interningfeature_validationfeature_external_gesfeature_external_pes all_featuresproperty_lexical_handler property_declaration_handlerproperty_dom_nodeproperty_xml_stringproperty_encodingproperty_interning_dictall_propertiesrR r r r <module>rn s 2\ \B 7 7 ( > N J > O Q #*("$$ & K S = A D P +#.%#) +*9 *9r