Minor adjustments to markup for the getDOMImplementation() description.

This commit is contained in:
Fred Drake 2001-11-30 16:58:15 +00:00
parent bd34b6bc3d
commit 89d63cc450

View file

@ -98,18 +98,21 @@ for the specific implementation (e.g. if that implementation supports
some customization). some customization).
\end{funcdesc} \end{funcdesc}
\begin{funcdesc}{getDOMImplementation}{name = None, features = ()} \begin{funcdesc}{getDOMImplementation}{\optional{name\optional{, features}}}
Return a suitable DOM implementation. The \var{name} is either Return a suitable DOM implementation. The \var{name} is either
well-known, the module name of a DOM implementation, or well-known, the module name of a DOM implementation, or
\code{None}. If it is not \code{None}, imports the corresponding module and \code{None}. If it is not \code{None}, imports the corresponding
returns a \class{DOMImplementation} object if the import succeeds. If module and returns a \class{DOMImplementation} object if the import
no name is given, and if the environment variable \envvar{PYTHON_DOM} is succeeds. If no name is given, and if the environment variable
set, this variable is used to find the implementation. \envvar{PYTHON_DOM} is set, this variable is used to find the
implementation.
If name is not given, consider the available implementations to find If name is not given, this examines the available implementations to
one with the required feature set. If no implementation can be found, find one with the required feature set. If no implementation can be
raise an \exception{ImportError}. The features list must be a sequence of found, raise an \exception{ImportError}. The features list must be a
(feature, version) pairs which are passed to hasFeature. sequence of \code{(\var{feature}, \var{version})} pairs which are
passed to the \method{hasFeature()} method on available
\class{DOMImplementation} objects.
\end{funcdesc} \end{funcdesc}