Commit e8ea7f5e authored by Fred Drake's avatar Fred Drake

Added \label{} for logical addressing.

parent b07c0871
...@@ -199,7 +199,10 @@ properly matching byte-compiled file (with suffix \code{.pyc}) exists, ...@@ -199,7 +199,10 @@ properly matching byte-compiled file (with suffix \code{.pyc}) exists,
it will be used instead of parsing the given source file. it will be used instead of parsing the given source file.
\end{funcdesc} \end{funcdesc}
\subsection{Examples} \subsection{Examples}
\label{examples-imp}
The following function emulates what was the standard import statement The following function emulates what was the standard import statement
up to Python 1.4 (i.e., no hierarchical module names). (This up to Python 1.4 (i.e., no hierarchical module names). (This
\emph{implementation} wouldn't work in that version, since \emph{implementation} wouldn't work in that version, since
......
...@@ -199,7 +199,10 @@ properly matching byte-compiled file (with suffix \code{.pyc}) exists, ...@@ -199,7 +199,10 @@ properly matching byte-compiled file (with suffix \code{.pyc}) exists,
it will be used instead of parsing the given source file. it will be used instead of parsing the given source file.
\end{funcdesc} \end{funcdesc}
\subsection{Examples} \subsection{Examples}
\label{examples-imp}
The following function emulates what was the standard import statement The following function emulates what was the standard import statement
up to Python 1.4 (i.e., no hierarchical module names). (This up to Python 1.4 (i.e., no hierarchical module names). (This
\emph{implementation} wouldn't work in that version, since \emph{implementation} wouldn't work in that version, since
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment