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
94a98e4f
Commit
94a98e4f
authored
Jul 06, 2006
by
Nick Coghlan
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update the tutorial section on relative imports
parent
56829d5b
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
25 additions
and
8 deletions
+25
-8
Doc/tut/tut.tex
Doc/tut/tut.tex
+25
-8
No files found.
Doc/tut/tut.tex
View file @
94a98e4f
...
...
@@ -2919,14 +2919,13 @@ submodules with the same name from different packages.
The submodules often need to refer to each other. For example, the
\module
{
surround
}
module might use the
\module
{
echo
}
module. In fact,
such references
are so common that the
\keyword
{
import
}
statement first looks in the
containing package before looking in the standard module search path.
Thus, the surround module can simply use
\code
{
import echo
}
or
\code
{
from echo import echofilter
}
. If the imported module is not
found in the current package
(
the package of which the current module
is a submodule
)
, the
\keyword
{
import
}
statement looks for a top
-
level
module with the given name.
such references are so common that the
\keyword
{
import
}
statement
first looks in the containing package before looking in the standard
module search path. Thus, the
\module
{
surround
}
module can simply use
\code
{
import echo
}
or
\code
{
from echo import echofilter
}
. If the
imported module is not found in the current package
(
the package of
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
...
...
@@ -2936,6 +2935,24 @@ must be used. For example, if the 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
\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
}
module for example, you might use:
\begin
{
verbatim
}
from . import echo
from .. import Formats
from ..Filters import equalizer
\end
{
verbatim
}
Note that both explicit and implicit relative imports are based on the
name of the current module. Since the name of the main module is always
\code
{
"
__
main
__
"
}
, modules intended for use as the main module of a
Python application should always use absolute imports.
\subsection
{
Packages in Multiple Directories
}
Packages support one more special attribute,
\member
{__
path
__}
. This
...
...
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