From: Fred Drake <fdrake@acm.org>
Date: Thu, 2 May 2002 21:37:23 +0000 (+0000)
Subject: Update the xrange object description to reflect the removal of deprecated
X-Git-Tag: v2.3c1~5730
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=b9032018ffaf6b4fb1eeeee44f9ee9ac0b407114;p=python

Update the xrange object description to reflect the removal of deprecated
features.
---

diff --git a/Doc/lib/libstdtypes.tex b/Doc/lib/libstdtypes.tex
index 0cd6289481..65e315239b 100644
--- a/Doc/lib/libstdtypes.tex
+++ b/Doc/lib/libstdtypes.tex
@@ -401,9 +401,9 @@ new buffer object.
 Xrange objects are similar to buffers in that there is no specific
 syntax to create them, but they are created using the
 \function{xrange()} function.\bifuncindex{xrange}  They don't support
-slicing or concatenation, but do support repetition, and using
-\code{in}, \code{not in}, \function{min()} or \function{max()} on them
-is inefficient.
+slicing, concatenation, or repetition, and using \keyword{in},
+\keyword{not} \keyword{in}, \function{min()} or \function{max()} on
+them is inefficient.
 \obindex{xrange}
 
 Most sequence types support the following operations.  The \samp{in} and