[Python-3000] optimizing [x]range

[Stargaming]

On Thu, 02 Aug 2007 21:43:14 +0200, Martin v. Löwis 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.
> 
> Regards,
> Martin

Fixed. Rewrote the patch for the p3yk branch. I'm not sure if I used the 
PyNumber-API correctly, I mostly oriented this patch at other range_* 
methods. See http://sourceforge.net/
tracker/index.php?func=detail&aid=1766304&group_id=5470&atid=305470

Regards,
Stargaming