Re: [Python-Dev] xrange accepting non-ints

2006-08-24 Thread Fredrik Lundh
Neal Norwitz wrote: > I've profiled various combinations. Here are the various results > normalized doing xrange(0, 1e6, 1): > > Run on all integer (32-bit) values for start, step, end: > C xrange and iter: 1 > Py xrange w/C iter: 1 in real life, loops are a lot shorter than that. if you take

Re: [Python-Dev] xrange accepting non-ints

2006-08-24 Thread Thomas Wouters
On 8/24/06, Guido van Rossum <[EMAIL PROTECTED]> wrote: On 8/24/06, Neal Norwitz <[EMAIL PROTECTED]> wrote:> I've been working on enhancing xrange and there are a bunch of issues> to consider.  I've got pretty much complete implementations in both C > and Python.  Currently xrange is 2 objects:  ra

Re: [Python-Dev] xrange accepting non-ints

2006-08-24 Thread Guido van Rossum
On 8/24/06, Neal Norwitz <[EMAIL PROTECTED]> wrote: > I've been working on enhancing xrange and there are a bunch of issues > to consider. I've got pretty much complete implementations in both C > and Python. Currently xrange is 2 objects: range and the iter. > These only work on C longs. Here'

[Python-Dev] xrange accepting non-ints

2006-08-24 Thread Neal Norwitz
I've been working on enhancing xrange and there are a bunch of issues to consider. I've got pretty much complete implementations in both C and Python. Currently xrange is 2 objects: range and the iter. These only work on C longs. Here's what I propose: 2.6: * Add deprecation warning if a floa