provided in the \code{formatter} module; refer to the documentation

for that module for information on the formatter interface.

\index{SGML}

\ttindex{SGMLParser}

\index{formatter}

The following is a summary of the interface defined by

\code{sgmllib.SGMLParser}:

This module defines a class which implements the client side of the

HTTP protocol. It is normally not used directly --- the module

\code{urllib} uses it to handle URLs that use HTTP.

The module defines one class, \code{HTTP}. An \code{HTTP} instance

represents one transaction with an HTTP server. It should be

to the reply code; and \var{headers} is an instance of the class

\code{mimetools.Message} containing the headers received from the server.

See the description of the \code{mimetools} module.

\end{funcdesc}

\begin{funcdesc}{getfile}{}

\code{pickle} and \code{shelve}. The \code{marshal} module exists

mainly to support reading and writing the ``pseudo-compiled'' code for

Python modules of \samp{.pyc} files.

\obindex{code}

Not all Python object types are supported; in general, only objects

to send them across a network or store them in a database. The module

\code{shelve} provides a simple interface to pickle and unpickle

objects on ``dbm''-style database files.

\strong{Note:} The \code{pickle} module is rather slow. A

reimplementation of the same algorithm in C, which is up to 1000 times

Unlike the built-in module \code{marshal}, \code{pickle} handles the

following correctly:

\begin{itemize}

long as \code{marshal} continues to be used for reading and writing

code objects), and at least this avoids the possibility of smuggling

Trojan horses into a program.

For the benefit of persistency modules written using \code{pickle}, it

supports the notion of a reference to an object outside the pickled

\strong{Do not import this module directly.} Instead, import the

module \code{os} and use \code{os.path}.

\renewcommand{\indexsubitem}{(in module posixpath)}

an initial \samp{\~\var{user}} is looked up in the password directory through

the built-in module \code{pwd}. If the expansion fails, or if the

path does not begin with a tilde, the path is returned unchanged.

\end{funcdesc}

\begin{funcdesc}{expandvars}{p}

\begin{funcdesc}{isfile}{p}

Return true if \var{p} is an existing regular file. This follows

\end{funcdesc}

\begin{funcdesc}{isdir}{p}

Return true if \var{p} is an existing directory. This follows

\end{funcdesc}

\begin{funcdesc}{islink}{p}

\begin{funcdesc}{samefile}{p\, q}

Return true if both pathname arguments refer to the same file or directory

(as indicated by device number and i-node number).

\end{funcdesc}

\begin{funcdesc}{split}{p}

(e.g. the \code{config.h} header file) are installed in the directory

\code{sys.exec_prefix+"/lib/python\emph{VER}/config"}, and shared library

modules are installed in

where \emph{VER} is equal to \code{sys.version[:3]}.

\end{datadesc}

(Typical use is \code{import pdb; pdb.pm()} to enter the post-mortem

debugger; see the chapter ``The Python Debugger'' for more

information.)

The meaning of the variables is the same

as that of the return values from \code{sys.exc_info()} above.

interpreter is invoked interactively or if the script is read from

standard input), \code{sys.path[0]} is the empty string, which directs

Python to search modules in the current directory first. Notice that

a result of \code{\$PYTHONPATH}.

\end{datadesc}

own prompts and (almost all of) its error messages go to

\code{sys.stderr}. \code{sys.stdout} and \code{sys.stderr} needn't

be built-in file objects: any object is acceptable as long as it has

objects doesn't affect the standard I/O streams of processes

executed by \code{popen()}, \code{system()} or the \code{exec*()}

family of functions in the \code{os} module.)

\end{datadesc}

\begin{datadesc}{tracebacklimit}

\code{__getinitargs__()}, \code{__getstate__()} and

\code{__setstate__()}. See the description of module \code{pickle}

for information on these methods.

\renewcommand{\indexsubitem}{(copy protocol)}

\ttindex{__getinitargs__}

\ttindex{__getstate__}

provided in the \code{formatter} module; refer to the documentation

for that module for information on the formatter interface.

\index{SGML}

\ttindex{SGMLParser}

\index{formatter}

The following is a summary of the interface defined by

\code{sgmllib.SGMLParser}:

This module defines a class which implements the client side of the

HTTP protocol. It is normally not used directly --- the module

\code{urllib} uses it to handle URLs that use HTTP.

The module defines one class, \code{HTTP}. An \code{HTTP} instance

represents one transaction with an HTTP server. It should be

to the reply code; and \var{headers} is an instance of the class

\code{mimetools.Message} containing the headers received from the server.

See the description of the \code{mimetools} module.

\end{funcdesc}

\begin{funcdesc}{getfile}{}