"bob gailer" <[EMAIL PROTECTED]> wrote
>> That's sad to see, I use range to generate lists of integers
>> almost as much as I use it for iteration.
> FWIW on my computer
> l = range(3000) takes under 0.19 seconds
> l = list(xrange(300)) under 0.27.
> So I don't think performance is an i
Alan Gauld wrote:
>> xrange() is being renamed to range(), so there will be no xrange()
>> and
>> range() will return an iterator rather than a list.
>>
>
> That's sad to see, I use range to generate lists of integers
> almost as much as I use it for iteration. But maybe I'm
> unusual in that
> xrange() is being renamed to range(), so there will be no xrange()
> and
> range() will return an iterator rather than a list.
That's sad to see, I use range to generate lists of integers
almost as much as I use it for iteration. But maybe I'm
unusual in that respect, I do use Python mainly for
Kent Johnson wrote:
> bob gailer wrote:
>
>
>> I disagree based on PEP 3100 (http://www.python.org/dev/peps/pep-3100/)
>>
>> Built-in Namespace:
>> - Make built-ins return an iterator where appropriate (e.g. range(),
>> zip(), map(), filter(), etc.)
>>
>> To be removed:
>> - xrange(): use range
bob gailer wrote:
> I disagree based on PEP 3100 (http://www.python.org/dev/peps/pep-3100/)
>
> Built-in Namespace:
> - Make built-ins return an iterator where appropriate (e.g. range(),
> zip(), map(), filter(), etc.)
>
> To be removed:
> - xrange(): use range() instead
Right, that's a good c
Andy Cheesman wrote:
> Hi people,
>
> After watching a nice Google video on Python 3K, and seeing the
> forthcoming removal of range,
I disagree based on PEP 3100 (http://www.python.org/dev/peps/pep-3100/)
Built-in Namespace:
- Make built-ins return an iterator where appropriate (e.g. range(),
Andy Cheesman wrote:
> After watching a nice Google video on Python 3K, and seeing the
> forthcoming removal of range, I've looked at substitution range with
> xrange within my code. Direct substitution works for 90% percent of the
> case (i.e. for thing in xrange(number): ), however i can't
Andy Cheesman wrote:
> Hi people,
>
> After watching a nice Google video on Python 3K, and seeing the
> forthcoming removal of range, I've looked at substitution range with
> xrange within my code. Direct substitution works for 90% percent of the
> case (i.e. for thing in xrange(number): ),
