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 differ
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
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 me
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 wil
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 Lebe
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 ove
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
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.va
> 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
>
> #
> On Wed, 11 May 2005, Danny Yoo wrote:
>
> > map(lambda x: x^2, [1, 2, 3])
> >
> > [x^2 for x in [1, 2, 3]]
> > then we're really saying something like this:
> >
> > [1, 2, 3]
> > | | |
> > | | | map()
> > | | |
> > V
It's not often I get a chance to correct Danny, but
On Wed, 11 May 2005, Danny Yoo wrote:
> map(lambda x: x^2, [1, 2, 3])
>
> [x^2 for x in [1, 2, 3]]
> then we're really saying something like this:
>
> [1, 2, 3]
> | | |
> | | | map()
Please tell them who reported them ;-)
Bernard
On 5/11/05, Danny Yoo <[EMAIL PROTECTED]> wrote:
>
>
> On Wed, 11 May 2005, Bernard Lebel wrote:
>
> > Thanks a lot for the advice. I will put that in practice.
> >
> > The blasphemous example is on page 227 of the second edition, under
> > Mapp
On Wed, 11 May 2005, Bernard Lebel wrote:
> Thanks a lot for the advice. I will put that in practice.
>
> The blasphemous example is on page 227 of the second edition, under
> Mapping Functions Over Sequences.
Hi Bernard,
Ah, thank you. I'll start the Inquisition shortly. *grin*
___
Hi Danny,
Thanks a lot for the advice. I will put that in practice.
The blasphemous example is on page 227 of the second edition, under
Mapping Functions Over Sequences.
Cheers
Bernard
On 5/11/05, Danny Yoo <[EMAIL PROTECTED]> wrote:
>
> > I have to confess that I already use map(), or shou
> I have to confess that I already use map(), or should I say abuse, for
> this, although it is the first time I consider using lambdas. Up until
> 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
> Learn
Hi Danny,
Thanks for the answer.
I have to confess that I already use map(), or should I say abuse, for
this, although it is the first time I consider using lambdas. Up until
now I always used map() to perform a looped call on a function that
would change the attribute value, as shown in Mark Lut
-- Forwarded message --
Date: Wed, 11 May 2005 14:29:58 -0400
From: Bernard Lebel <[EMAIL PROTECTED]>
To: Danny Yoo <[EMAIL PROTECTED]>
Subject: Re: [Tutor] map() and lambda to change class instance attribute
Hi Danny,
Thanks for the answer.
I have to confess th
> It is possible to abuse map() to do what you're trying to do, using the
> setattr() function:
>
> ## Pseudocode
> map(lambda instance: setattr(instance, 'value', 42))
> ##
Hi Bernard,
Grrr... I did label that as Pseudocode, but that doesn't excuse me from
not actually trying to make t
On Wed, 11 May 2005, Bernard Lebel wrote:
> Let say I have several class instances in a list, and these class
> instances have an attribute named "value", whose value is an integer.
>
> I would like to know if it is possible to loop over the list of
> instances to change their "value" attribute,
Hello,
Let say I have several class instances in a list, and these class
instances have an attribute named "value", whose value is an integer.
I would like to know if it is possible to loop over the list of
instances to change their "value" attribute, using a map( (
lambda:...), ... ) type of loo
20 matches
Mail list logo
