Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
52c0c368
Commit
52c0c368
authored
Aug 07, 2007
by
Georg Brandl
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Bug #1769002: fix a now-wrong sentence in the tutorial.
parent
e7fe6c3d
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
7 deletions
+6
-7
Doc/tut/tut.tex
Doc/tut/tut.tex
+6
-7
No files found.
Doc/tut/tut.tex
View file @
52c0c368
...
...
@@ -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
}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment