summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>2001-12-14 22:55:14 (GMT)
committerFred Drake <fdrake@acm.org>2001-12-14 22:55:14 (GMT)
commit08d752cf28619ecac70ff3528fd8d020378b007b (patch)
treecfa0160e6051e204162c0f327913edf2bf0f5703
parent75401a0214c25fcc4b2d66459ddf7842b52c8273 (diff)
downloadcpython-08d752cf28619ecac70ff3528fd8d020378b007b.zip
cpython-08d752cf28619ecac70ff3528fd8d020378b007b.tar.gz
cpython-08d752cf28619ecac70ff3528fd8d020378b007b.tar.bz2
Update to use the notice environment so a multi-paragraph note can be
appropriately marked.
-rw-r--r--Doc/ref/ref6.tex6
1 files changed, 4 insertions, 2 deletions
diff --git a/Doc/ref/ref6.tex b/Doc/ref/ref6.tex
index 3089b1a..122f499 100644
--- a/Doc/ref/ref6.tex
+++ b/Doc/ref/ref6.tex
@@ -482,14 +482,16 @@ difficulty is that there's no guarantee the generator will ever be
resumed, hence no guarantee that the \keyword{finally} block will ever
get executed.
-\note{In Python 2.2, the \keyword{yield} statement is only allowed
+\begin{notice}
+In Python 2.2, the \keyword{yield} statement is only allowed
when the \code{generators} feature has been enabled. It will always
be enabled in Python 2.3. This \code{__future__} import statment can
-be used to enable the feature:}
+be used to enable the feature:
\begin{verbatim}
from __future__ import generators
\end{verbatim}
+\end{notice}
\begin{seealso}