# cpython-withatomic / Doc / libxmllib.tex

The branch 'legacy-trunk' does not exist.
  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 \section{Standard Module \sectcode{xmllib}} % Author: Sjoerd Mullender \label{module-xmllib} \stmodindex{xmllib} \index{XML} This module defines a class \code{XMLParser} which serves as the basis for parsing text files formatted in XML (eXtended Markup Language). The \code{XMLParser} class must be instantiated without arguments. It has the following interface methods: \renewcommand{\indexsubitem}{(XMLParser method)} \begin{funcdesc}{reset}{} Reset the instance. Loses all unprocessed data. This is called implicitly at the instantiation time. \end{funcdesc} \begin{funcdesc}{setnomoretags}{} Stop processing tags. Treat all following input as literal input (CDATA). \end{funcdesc} \begin{funcdesc}{setliteral}{} Enter literal mode (CDATA mode). \end{funcdesc} \begin{funcdesc}{feed}{data} Feed some text to the parser. It is processed insofar as it consists of complete elements; incomplete data is buffered until more data is fed or \code{close()} is called. \end{funcdesc} \begin{funcdesc}{close}{} Force processing of all buffered data as if it were followed by an end-of-file mark. This method may be redefined by a derived class to define additional processing at the end of the input, but the redefined version should always call \code{XMLParser.close()}. \end{funcdesc} \begin{funcdesc}{handle_starttag}{tag\, method\, attributes} This method is called to handle start tags for which a \code{start_\var{tag}()} method has been defined. The \code{tag} argument is the name of the tag, and the \code{method} argument is the bound method which should be used to support semantic interpretation of the start tag. The \var{attributes} argument is a dictionary of attributes, the key being the \var{name} and the value being the \var{value} of the attribute found inside the tag's \code{<>} brackets. Lower case and double quotes and backslashes in the \var{value} have been interpreted. For instance, for the tag \code{}, this method would be called as \code{handle_starttag('A', self.start_A, \{'HREF': 'http://www.cwi.nl/'\})}. The base implementation simply calls \code{method} with \code{attributes} as the only argument. \end{funcdesc} \begin{funcdesc}{handle_endtag}{tag\, method} This method is called to handle endtags for which an \code{end_\var{tag}()} method has been defined. The \code{tag} argument is the name of the tag, and the \code{method} argument is the bound method which should be used to support semantic interpretation of the end tag. If no \code{end_\var{tag}()} method is defined for the closing element, this handler is not called. The base implementation simply calls \code{method}. \end{funcdesc} \begin{funcdesc}{handle_data}{data} This method is called to process arbitrary data. It is intended to be overridden by a derived class; the base class implementation does nothing. \end{funcdesc} \begin{funcdesc}{handle_charref}{ref} This method is called to process a character reference of the form \code{\&\#\var{ref};}''. \var{ref} can either be a decimal number, or a hexadecimal number when preceded by \code{x}. In the base implementation, \var{ref} must be a number in the range 0-255. It translates the character to \ASCII{} and calls the method \code{handle_data()} with the character as argument. If \var{ref} is invalid or out of range, the method \code{unknown_charref(\var{ref})} is called to handle the error. A subclass must override this method to provide support for character references outside of the \ASCII{} range. \end{funcdesc} \begin{funcdesc}{handle_entityref}{ref} This method is called to process a general entity reference of the form \code{\&\var{ref};}'' where \var{ref} is an general entity reference. It looks for \var{ref} in the instance (or class) variable \code{entitydefs} which should be a mapping from entity names to corresponding translations. If a translation is found, it calls the method \code{handle_data()} with the translation; otherwise, it calls the method \code{unknown_entityref(\var{ref})}. The default \code{entitydefs} defines translations for \code{\&}, \code{\&apos}, \code{\>}, \code{\<}, and \code{\"}. \end{funcdesc} \begin{funcdesc}{handle_comment}{comment} This method is called when a comment is encountered. The \code{comment} argument is a string containing the text between the \code{}'' delimiters, but not the delimiters themselves. For example, the comment \code{}'' will cause this method to be called with the argument \code{'text'}. The default method does nothing. \end{funcdesc} \begin{funcdesc}{handle_cdata}{data} This method is called when a CDATA element is encountered. The \code{data} argument is a string containing the text between the \code{}'' delimiters, but not the delimiters themselves. For example, the entity \code{}'' will cause this method to be called with the argument \code{'text'}. The default method does nothing. \end{funcdesc} \begin{funcdesc}{handle_proc}{name\, data} This method is called when a processing instruction (PI) is encountered. The \code{name} is the PI target, and the \code{data} argument is a string containing the text between the PI target and the closing delimiter, but not the delimiter itself. For example, the instruction \code{}'' will cause this method to be called with the arguments \code{'XML'} and \code{'text'}. The default method does nothing. \end{funcdesc} \begin{funcdesc}{handle_special}{data} This method is called when a declaration is encountered. The \code{data} argument is a string containing the text between the \code{}'' delimiters, but not the delimiters themselves. For example, the entity \code{}'' will cause this method to be called with the argument \code{'DOCTYPE text'}. The default method does nothing. \end{funcdesc} \begin{funcdesc}{syntax_error}{lineno\, message} This method is called when a syntax error is encountered. The \code{lineno} argument is the line number of the error, and the \code{message} is a description of what was wrong. The default method raises a \code{RuntimeError} exception. If this method is overridden, it is permissable for it to return. This method is only called when the error can be recovered from. \end{funcdesc} \begin{funcdesc}{unknown_starttag}{tag\, attributes} This method is called to process an unknown start tag. It is intended to be overridden by a derived class; the base class implementation does nothing. \end{funcdesc} \begin{funcdesc}{unknown_endtag}{tag} This method is called to process an unknown end tag. It is intended to be overridden by a derived class; the base class implementation does nothing. \end{funcdesc} \begin{funcdesc}{unknown_charref}{ref} This method is called to process unresolvable numeric character references. It is intended to be overridden by a derived class; the base class implementation does nothing. \end{funcdesc} \begin{funcdesc}{unknown_entityref}{ref} This method is called to process an unknown entity reference. It is intended to be overridden by a derived class; the base class implementation does nothing. \end{funcdesc} Apart from overriding or extending the methods listed above, derived classes may also define methods of the following form to define processing of specific tags. Tag names in the input stream are case dependent; the \var{tag} occurring in method names must be in the correct case: \begin{funcdesc}{start_\var{tag}}{attributes} This method is called to process an opening tag \var{tag}. The \var{attributes} argument has the same meaning as described for \code{handle_starttag()} above. \end{funcdesc} \begin{funcdesc}{end_\var{tag}}{} This method is called to process a closing tag \var{tag}. \end{funcdesc} 
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.