>> Adaptation looks very promising. I just wish it didn't require all =
that extra typing....
Ian Bicking wrote (in response to the above)...
>It should usually take less typing. You need only adapt at the last
>moment, so you pass objects through based on the expectation they will
>later be adapted if necessary. =20
I really meant that Interfaces mean its no longer enough to create a =
class. I now need to create an Interface "prototype" and then classes =
that implement that Interface. One of the great things about Python (for =
me) is that you can say "Does it quack? Ok, lets assume its a duck" =
without a lot of rigmarole. I'm probably showing my (deep) ignorance but =
the whole Interfaces thing seems to be putting the rigmarole back in.
Its kind of a comfort that the very bright people involved with Twisted =
and Zope are making big use of Interfaces but at the same time these =
projects are noted for their use of python to create things that do not =
appear to be very pythonic (Aquisition? reliance on Callbacks?)
>But I'm still getting used to it as a paradigm -- I think it will be a
>very big deal, but I don't think it's widely understood, even by those
>(like me) that are using it.
Which is probably why I should do more research into this instead of =
whining about having to do a bit more typing....
From: Ian Bicking [mailto:ianb@...]
Sent: Monday, January 12, 2004 11:16 AM
To: Ian Sparks
Cc: Sqlobject-Discuss@.... Sourceforge. Net (E-mail)
Subject: RE: [SQLObject] SQLObject & Webware FormKit Integration
On Mon, 2004-01-12 at 15:38, Ian Sparks wrote:
> Thanks for the update on this and on the Archetypes & PyProtocols =
links. They make=20
> for interesting reading. Is PyProtocols stable?=20
Yes, I think it's pretty stable. It's a core part of PEAK, and it's
fairly mature. I'm sure Zope 3 and Twisted's adaptation are fairly
mature too (again because they are fundamental building blocks for those
platforms), but PyProtocols was the only one with decent documentation
(and isolated distribution).
> Adaptation looks very promising. I just wish it didn't require all =
that extra typing....
It should usually take less typing. You need only adapt at the last
moment, so you pass objects through based on the expectation they will
later be adapted if necessary. In FormEncode there's the toPython and
fromPython functions, which actually do the necessary adaptation
themselves then call the appropriate method, so there's really no extra
typing at all.
But I'm still getting used to it as a paradigm -- I think it will be a
very big deal, but I don't think it's widely understood, even by those
(like me) that are using it. Well, I understand the mechanism, but
that's different from having an intuition on how it should best be
used. And I don't feel like there's many other languages that provide a
model for how it might work -- it's really very novel, at least from my