On Tue, Apr 8, 2008 at 11:45 PM, Anand Balachandran Pillai <[EMAIL PROTECTED]> wrote: > Still this seems like a bad thing to break backward compatibility with.
That's not a very strong argument for Py3k. > Hopefully, this will be well documented at 3.0 release. Currently > that "whats new" page does not mention anything about the range > type and how it breaks backward compatibility. > > The NEWS page for 3.0 a4 does say this however. > > "range() now returns an iterator rather than a list. Floats are not allowed. > xrange() is no longer defined." > > I guess more information can be added here to actually specify > that range() returns not just any iterator, but an iterator which is a new > type and how it is different. Please submit a doc patch! -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
