Well, that was a nice explanation. Thanks once again Kent!
Bernard
On 5/16/05, Kent Johnson [EMAIL PROTECTED] wrote:
Bernard Lebel wrote:
Hi Kent,
So if I undestand you right, mapping a function with map() when it is
a built-in function will/may be faster than a for loop, but if it's a
That is very interesting John. Thanks!
Bernard
On 5/19/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Quoting Bernard Lebel [EMAIL PROTECTED]:
Well, that was a nice explanation. Thanks once again Kent!
There is a nice (not too technical) essay on the running speeds of different
Bernard Lebel wrote:
Hi Kent,
So if I undestand you right, mapping a function with map() when it is
a built-in function will/may be faster than a for loop, but if it's a
custom function (ie. a def one), it will most likely be slower?
I guess I didn't proofread that last mail...what I meant
Thanks Alan, that clears things up quite well.
Bernard
On 5/14/05, Alan Gauld [EMAIL PROTECTED] wrote:
So if I undestand you right, mapping a function with map()
when it is a built-in function will/may be faster than a for
loop, but if it's a custom function (ie. a def one), it will
now I always used map() to perform a looped call on a function that
would change the attribute value, as shown in Mark Lutz David
Ascher's Learning Python:
# Perform attribute value change on a single instance
def iterateInstances( oInstance ):
oInstance.value = myValue
# Loop over
Alan Gauld wrote:
now I always used map() to perform a looped call on a function that
would change the attribute value, as shown in Mark Lutz David
Ascher's Learning Python:
# Perform attribute value change on a single instance
def iterateInstances( oInstance ):
oInstance.value = myValue
The authors even go as far as saysing, on page 228 (first paragraph)
that map() used that way has a performance benefit and is faster than
a for loop.
Cheers
Bernard
On 5/13/05, Alan Gauld [EMAIL PROTECTED] wrote:
How bizarre. I'm astonished that Lutz/Ascher even show that as a means
of
Bernard Lebel wrote:
The authors even go as far as saysing, on page 228 (first paragraph)
that map() used that way has a performance benefit and is faster than
a for loop.
That may well be correct, at least in the case where the function passed to map
is a builtin.
Mapping a builtin to over
Hi Kent,
So if I undestand you right, mapping a function with map() when it is
a built-in function will/may be faster than a for loop, but if it's a
custom function (ie. a def one), it will most likely be slower?
Thanks
Bernard
On 5/13/05, Kent Johnson [EMAIL PROTECTED] wrote:
Bernard Lebel
