summaryrefslogtreecommitdiffstats
path: root/Doc/ref/ref6.tex
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>2003-07-15 22:03:00 (GMT)
committerFred Drake <fdrake@acm.org>2003-07-15 22:03:00 (GMT)
commitd51ce7de97f3aa1cf6ee65975475dce371cd3aea (patch)
tree725fb8139c358c87e77f92f9475c4a8b6a9d663f /Doc/ref/ref6.tex
parent4e72e0533d30f56ad3fb05f761e0283a26a1e64d (diff)
downloadcpython-d51ce7de97f3aa1cf6ee65975475dce371cd3aea.zip
cpython-d51ce7de97f3aa1cf6ee65975475dce371cd3aea.tar.gz
cpython-d51ce7de97f3aa1cf6ee65975475dce371cd3aea.tar.bz2
Indexing is a mess; try to get the link targets closer to the relevant
text. There needs to be a better way.
Diffstat (limited to 'Doc/ref/ref6.tex')
-rw-r--r--Doc/ref/ref6.tex20
1 files changed, 9 insertions, 11 deletions
diff --git a/Doc/ref/ref6.tex b/Doc/ref/ref6.tex
index 00b7c78..4e966bf 100644
--- a/Doc/ref/ref6.tex
+++ b/Doc/ref/ref6.tex
@@ -660,18 +660,16 @@ given as \code{sys.path}.
\indexii{filename}{extension}
\indexiii{module}{search}{path}
-If a built-in module is found, its built-in initialization code is
-executed and step (1) is finished. If no matching file is found,
-\exception{ImportError} is raised. If a file is found, it is parsed,
+If a built-in module is found,\indexii{module}{initialization} its
+built-in initialization code is executed and step (1) is finished. If
+no matching file is found,
+\exception{ImportError}\exindex{ImportError} is raised.
+\index{code block}If a file is found, it is parsed,
yielding an executable code block. If a syntax error occurs,
-\exception{SyntaxError} is raised. Otherwise, an empty module of the given
-name is created and inserted in the module table, and then the code
-block is executed in the context of this module. Exceptions during
-this execution terminate step (1).
-\indexii{module}{initialization}
-\exindex{SyntaxError}
-\exindex{ImportError}
-\index{code block}
+\exception{SyntaxError}\exindex{SyntaxError} is raised. Otherwise, an
+empty module of the given name is created and inserted in the module
+table, and then the code block is executed in the context of this
+module. Exceptions during this execution terminate step (1).
When step (1) finishes without raising an exception, step (2) can
begin.