mirror of
https://github.com/python/cpython.git
synced 2025-11-01 10:45:30 +00:00
Make the embedded hyperlinks work.
This commit is contained in:
parent
b36615d584
commit
984920bbad
1 changed files with 7 additions and 6 deletions
|
|
@ -86,10 +86,10 @@ by executing:
|
|||
from __future__ import division
|
||||
\end{verbatim}
|
||||
|
||||
the expression \code{11/4} would evaluate to \code{2.75}. By
|
||||
actually importing the \refmodule[future]{__future__} module and
|
||||
evaluating its variables, you can see when a new feature was first
|
||||
added to the language and when it will become the default:
|
||||
the expression \code{11/4} would evaluate to \code{2.75}. By actually
|
||||
importing the \ulink{\module{__future__}}{../lib/module-future.html}
|
||||
module and evaluating its variables, you can see when a new feature
|
||||
was first added to the language and when it will become the default:
|
||||
|
||||
\begin{verbatim}
|
||||
>>> import __future__
|
||||
|
|
@ -256,8 +256,9 @@ distinguished by their namespaces. Namespaces also aid readability
|
|||
and maintainability by making it clear which modules implement a
|
||||
function. For instance, writing \function{random.seed()} or
|
||||
{}\function{itertools.izip()} makes it clear that those functions are
|
||||
implemented by the \refmodule{random} and \refmodule{itertools}
|
||||
modules respectively.
|
||||
implemented by the \ulink{\module{random}}{../lib/module-random.html}
|
||||
and \ulink{\module{itertools}}{../lib/module-itertools.html} modules
|
||||
respectively.
|
||||
|
||||
\index{nested scope}
|
||||
\item[nested scope]
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue