cinap_lenrekadd hg and python4bb9e2215 years agoHistory
63 lines · 2.4 KB · TeX
RawDownload
\section{\module{ni} ---         None}\declaremodule{standard}{ni} \modulesynopsis{None}  \strong{Warning: This module is obsolete.}  As of Python 1.5a4,package support (with different semantics for \code{__init__} and nosupport for \code{__domain__} or \code{__}) is built in theinterpreter.  The ni module is retained only for backwardcompatibility.  As of Python 1.5b2, it has been renamed to \code{ni1}; if you really need it, you can use \code{import ni1}, but therecommended approach is to rely on the built-in package support,converting existing packages if needed.  Note that mixing \code{ni}and the built-in package support doesn't work: once you import\code{ni}, all packages use it. The \code{ni} module defines a new importing scheme, which supportspackages containing several Python modules.  To enable packagesupport, execute \code{import ni} before importing any packages.  Importingthis module automatically installs the relevant import hooks.  Thereare no publicly-usable functions or variables in the \code{ni} module. To create a package named \code{spam} containing sub-modules \code{ham}, \code{bacon} and\code{eggs}, create a directory \file{spam} somewhere on Python's module searchpath, as given in \code{sys.path}.  Then, create files called \file{ham.py}, \file{bacon.py} and\file{eggs.py} inside \file{spam}. To import module \code{ham} from package \code{spam} and use function\code{hamneggs()} from that module, you can use any of the followingpossibilities: \begin{verbatim}import spam.ham		# *not* "import spam" !!!spam.ham.hamneggs()\end{verbatim}%\begin{verbatim}from spam import hamham.hamneggs()\end{verbatim}%\begin{verbatim}from spam.ham import hamneggshamneggs()\end{verbatim}%\code{import spam} creates anempty package named \code{spam} if one does not already exist, but it does\emph{not} automatically import \code{spam}'s submodules.  The only submodule that is guaranteed to be imported is\code{spam.__init__}, if it exists; it would be in a file named\file{__init__.py} in the \file{spam} directory.  Note that\code{spam.__init__} is a submodule of package spam.  It can refer tospam's namespace as \code{__} (two underscores): \begin{verbatim}__.spam_inited = 1		# Set a package-level variable\end{verbatim}%Additional initialization code (setting up variables, importing othersubmodules) can be performed in \file{spam/__init__.py}.