traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Bug #1769002: fix a now-wrong sentence in the tutorial. 

(backport from rev. 56797)
This commit is contained in:
Georg Brandl 2007-08-07 07:13:27 +00:00
parent 36fe3c0a84
commit e51d1d11f0
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
Doc/tut/tut.tex
View File

@ -2966,15 +2966,14 @@ which the current module is a submodule), the \keyword{import}
statement looks for a top-level module with the given name.
When packages are structured into subpackages (as with the
\module{sound} package in the example), there's no shortcut to refer
to submodules of sibling packages - the full name of the subpackage
must be used. For example, if the module
\module{sound.filters.vocoder} needs to use the \module{echo} module
in the \module{sound.effects} package, it can use \code{from
sound.effects import echo}.
\module{sound} package in the example), you can use absolute
imports to refer to submodules of siblings packages.
For example, if the module \module{sound.filters.vocoder} needs to
use the \module{echo} module in the \module{sound.effects} package,
it can use \code{from sound.effects import echo}.
Starting with Python 2.5, in addition to the implicit relative imports
described above, you can write explicit relative imports with the
described above, you can also write explicit relative imports with the
\code{from module import name} form of import statement. These explicit
relative imports use leading dots to indicate the current and parent
packages involved in the relative import. From the \module{surround}