From: Georg Brandl Date: Tue, 7 Aug 2007 07:13:27 +0000 (+0000) Subject: Bug #1769002: fix a now-wrong sentence in the tutorial. X-Git-Tag: v2.5.2c1~221 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=e51d1d11f0fb949c6a8d8ba8fea6330fc3a1ac58;p=python Bug #1769002: fix a now-wrong sentence in the tutorial. (backport from rev. 56797) --- diff --git a/Doc/tut/tut.tex b/Doc/tut/tut.tex index 61d0db5060..d6fc75bc66 100644 --- a/Doc/tut/tut.tex +++ b/Doc/tut/tut.tex @@ -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}