Sure. The 3.0 range() isn't exactly the same as the 2.6 xrange(), so
it would have to be a proper backport (sorry, I don't recall the exact
difference, but I remember it's been redone, perhaps to support long
integers).
It seems pretty minor though. The advantage of using xrange() is that
you remain backwards compatible all the way to 2.0 and probably even
1.5.2...
On Fri, Mar 14, 2008 at 8:14 PM, Eric Smith
<[EMAIL PROTECTED]> wrote:
> In the keynote, Guido mentioned switching from range to xrange in 2.6
> code, as a migration strategy. Another option would be to add range to
> future_builtins, and have it call xrange. Would that be desirable?
--
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
