Merged revisions 55007-55179 via svnmerge from
svn+ssh://pythondev@svn.python.org/python/branches/p3yk
........
r55077 | guido.van.rossum | 2007-05-02 11:54:37 -0700 (Wed, 02 May 2007) | 2 lines
Use the new print syntax, at least.
........
r55142 | fred.drake | 2007-05-04 21:27:30 -0700 (Fri, 04 May 2007) | 1 line
remove old cruftiness
........
r55143 | fred.drake | 2007-05-04 21:52:16 -0700 (Fri, 04 May 2007) | 1 line
make this work with the new Python
........
r55162 | neal.norwitz | 2007-05-06 22:29:18 -0700 (Sun, 06 May 2007) | 1 line
Get asdl code gen working with Python 2.3. Should continue to work with 3.0
........
r55164 | neal.norwitz | 2007-05-07 00:00:38 -0700 (Mon, 07 May 2007) | 1 line
Verify checkins to p3yk (sic) branch go to 3000 list.
........
r55166 | neal.norwitz | 2007-05-07 00:12:35 -0700 (Mon, 07 May 2007) | 1 line
Fix this test so it runs again by importing warnings_test properly.
........
r55167 | neal.norwitz | 2007-05-07 01:03:22 -0700 (Mon, 07 May 2007) | 8 lines
So long xrange. range() now supports values that are outside
-sys.maxint to sys.maxint. floats raise a TypeError.
This has been sitting for a long time. It probably has some problems and
needs cleanup. Objects/rangeobject.c now uses 4-space indents since
it is almost completely new.
........
r55171 | guido.van.rossum | 2007-05-07 10:21:26 -0700 (Mon, 07 May 2007) | 4 lines
Fix two tests that were previously depending on significant spaces
at the end of a line (and before that on Python 2.x print behavior
that has no exact equivalent in 3.0).
........
diff --git a/Doc/lib/libfuncs.tex b/Doc/lib/libfuncs.tex
index 0900317..c02f6f1 100644
--- a/Doc/lib/libfuncs.tex
+++ b/Doc/lib/libfuncs.tex
@@ -868,7 +868,7 @@
\end{funcdesc}
\begin{funcdesc}{range}{\optional{start,} stop\optional{, step}}
- This is a versatile function to create lists containing arithmetic
+ This is a versatile function to create sequences containing arithmetic
progressions. It is most often used in \keyword{for} loops. The
arguments must be plain integers. If the \var{step} argument is
omitted, it defaults to \code{1}. If the \var{start} argument is
@@ -882,19 +882,19 @@
\exception{ValueError} is raised). Example:
\begin{verbatim}
->>> range(10)
+>>> list(range(10))
[0, 1, 2, 3, 4, 5, 6, 7, 8, 9]
->>> range(1, 11)
+>>> list(range(1, 11))
[1, 2, 3, 4, 5, 6, 7, 8, 9, 10]
->>> range(0, 30, 5)
+>>> list(range(0, 30, 5))
[0, 5, 10, 15, 20, 25]
->>> range(0, 10, 3)
+>>> list(range(0, 10, 3))
[0, 3, 6, 9]
->>> range(0, -10, -1)
+>>> list(range(0, -10, -1))
[0, -1, -2, -3, -4, -5, -6, -7, -8, -9]
->>> range(0)
+>>> list(range(0))
[]
->>> range(1, 0)
+>>> list(range(1, 0))
[]
\end{verbatim}
\end{funcdesc}
@@ -1230,24 +1230,6 @@
other scopes (such as modules) can be. This may change.}
\end{funcdesc}
-\begin{funcdesc}{xrange}{\optional{start,} stop\optional{, step}}
- This function is very similar to \function{range()}, but returns an
- ``xrange object'' instead of a list. This is an opaque sequence
- type which yields the same values as the corresponding list, without
- actually storing them all simultaneously. The advantage of
- \function{xrange()} over \function{range()} is minimal (since
- \function{xrange()} still has to create the values when asked for
- them) except when a very large range is used on a memory-starved
- machine or when all of the range's elements are never used (such as
- when the loop is usually terminated with \keyword{break}).
-
- \note{\function{xrange()} is intended to be simple and fast.
- Implementations may impose restrictions to achieve this.
- The C implementation of Python restricts all arguments to
- native C longs ("short" Python integers), and also requires
- that the number of elements fit in a native C long.}
-\end{funcdesc}
-
\begin{funcdesc}{zip}{\optional{iterable, \moreargs}}
This function returns a list of tuples, where the \var{i}-th tuple contains
the \var{i}-th element from each of the argument sequences or iterables.