1berry/cpython
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Added more warnings about ni's demise.

Browse Source
This commit is contained in:
Guido van Rossum 1997-12-09 15:03:41 +00:00
parent 7b8970ac88
commit 138dac5a1b
2 changed files with 14 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
Doc/lib/libni.tex
View File

@ -4,9 +4,14 @@
\strong{Warning: This module is obsolete.} As of Python 1.5a4, \strong{Warning: This module is obsolete.} As of Python 1.5a4,
package support (with different semantics for \code{__init__} and no package support (with different semantics for \code{__init__} and no
support for \code{__domain__} or\code{__}) is built in the support for \code{__domain__} or \code{__}) is built in the
interpreter. The ni module is retained only for backward interpreter. The ni module is retained only for backward
compatibility. compatibility. As of Python 1.5b2, it has been renamed to \code{ni1};
if you really need it, you can use \code{import ni1}, but the
recommended 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 supports The \code{ni} module defines a new importing scheme, which supports
packages containing several Python modules. To enable package packages containing several Python modules. To enable package

9
Doc/libni.tex
View File

@ -4,9 +4,14 @@
\strong{Warning: This module is obsolete.} As of Python 1.5a4, \strong{Warning: This module is obsolete.} As of Python 1.5a4,
package support (with different semantics for \code{__init__} and no package support (with different semantics for \code{__init__} and no
support for \code{__domain__} or\code{__}) is built in the support for \code{__domain__} or \code{__}) is built in the
interpreter. The ni module is retained only for backward interpreter. The ni module is retained only for backward
compatibility. compatibility. As of Python 1.5b2, it has been renamed to \code{ni1};
if you really need it, you can use \code{import ni1}, but the
recommended 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 supports The \code{ni} module defines a new importing scheme, which supports
packages containing several Python modules. To enable package packages containing several Python modules. To enable package