[Python-3000] optimizing [x]range

[Guido van Rossum]

On 8/2/07, "Martin v. Löwis" <martin at v.loewis.de> wrote:
> > The patch is based on the latest trunk/ checkout, Python 2.6. I don't
> > think this is a problem if nobody else made any effort towards making
> > xrange more sequence-like in the Python 3000 branch. The C source might
> > require some tab/space cleanup.
>
> Unfortunately, this is exactly what happened: In Py3k, the range object
> is defined in terms PyObject*, so your patch won't apply to the 3k branch.

FWIW, making xrange (or range in Py3k) "more sequence-like" is exactly
what should *not* happen.

-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)