Update the xrange object description to reflect the removal of deprecated

features.
This commit is contained in:
Fred Drake 2002-05-02 21:37:23 +00:00
parent d0ba636541
commit b9032018ff
1 changed files with 3 additions and 3 deletions

View File

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