I don't understand the implications of this article but it may have an impact
on dabo in
general..
http://www.canonical.org/~kragen/isinstance/
Cheers,
Larry Long
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_
On Sep 17, 2009, at 10:12 PM, lalo...@charter.net wrote:
> I don't understand the implications of this article but it may have
> an impact on dabo in
> general..
>
> http://www.canonical.org/~kragen/isinstance/
It's simply a matter of purists unable to understand the real world.
-- Ed
Ed Leafe wrote:
> On Sep 17, 2009, at 10:12 PM, lalo...@charter.net wrote:
>
>> I don't understand the implications of this article but it may have
>> an impact on dabo in
>> general..
>>
>> http://www.canonical.org/~kragen/isinstance/
>
> It's simply a matter of purists unable to underst
Paul McNett wrote:
> Ed Leafe wrote:
>> On Sep 17, 2009, at 10:12 PM, lalo...@charter.net wrote:
>>
>>> I don't understand the implications of this article but it may have
>>> an impact on dabo in
>>> general..
>>>
>>> http://www.canonical.org/~kragen/isinstance/
>> It's simply a matter of p
On Thu, Sep 17, 2009 at 08:43:53PM -0700, Paul McNett wrote:
> On a more serious note, rest assured if something practical were affected by
> our
> gratuitous use of isinstance(), we'd change it.
>
> Usually, we don't care if an object supports an interface, we care if the
> object is
> an ins
Roger Gammans wrote:
> def setColExpand(self, expand, colNum, proportion=0):
> """ Sets the 'growable' status of one or more columns. """
> # If the colNum argument was passed first, switch it
> # with the
> # expand argument
> if isinstance(expand, basestring):
>
Paul McNett wrote:
> Roger Gammans wrote:
>> It is a difficult issue, and isinstance is a easy crutch to fall
>> into using , and I'm sure parts of my own code suffer from this
>> as well.
>
> Patches are welcome! :)
Specifically, if someone wanted to take this on, I'd want to see some functions
On Friday 18 September 2009 06:46:49 am Paul McNett wrote:
> Paul McNett wrote:
> > Roger Gammans wrote:
> >> It is a difficult issue, and isinstance is a easy crutch to fall
> >> into using , and I'm sure parts of my own code suffer from this
> >> as well.
> >
> > Patches are welcome! :)
>
> Speci
John wrote:
> If the developer is moving from VFP it maybe easier to understand or read.
> But as the developer becomes used to reading python I see the opposite
> effect.
Why does VFP have anything to do with this? Shorter strings, where each
communicates
the same meaning, are going to be
On Friday 18 September 2009 07:54:55 am Paul McNett wrote:
> John wrote:
> > If the developer is moving from VFP it maybe easier to understand or
> > read. But as the developer becomes used to reading python I see the
> > opposite effect.
>
> Why does VFP have anything to do with this? Shorter stri
John wrote:
> I disagree with the last statement of easier to read.
I've spent more time on this already than my interest level in it. If someone
wants
to pursue replacing isinstance() with "better" code that is more
interface-based,
then they can take this argument up with you.
Paul
In a message dated 9/18/2009 2:30:36 P.M. Eastern Daylight Time,
p...@ulmcnett.com writes:
John wrote:
> I disagree with the last statement of easier to read.
I've spent more time on this already than my interest level in it. If
someone wants
to pursue replacing isinstance() with "better
On Sep 18, 2009, at 1:30 PM, Paul McNett wrote:
> I've spent more time on this already than my interest level in it.
I got turned off by the "considered harmful" tone of the article. If
it had been simply stated that you should support duck typing wherever
possible, or use try/except
13 matches
Mail list logo
