[Zope-dev] implementing zope.component 4.0
Martijn Faassen
faassen at startifact.com
Fri Nov 27 08:38:55 EST 2009
Marius Gedminas wrote:
[snip]
> +0.5 --- I can live with it. Backwards incompatibility with IFoo(one,
> default) will be a slight inconvenience. There were proposals I liked
> more (IFoo.adapt(), IFoo.utility()) and proposals I liked less
> (IFoo((one, two, we_like_parentheses, and_screw_people_adapting_tuples))).
I'd ask people to think about this approach without considering
backwards compatibility issues first. Especially given the goal "making
component lookup disappear into the language" makes me think just all
making it calling an interface would be the most elegant approach.
So imagining we didn't have to worry about backwards compatibility,
would you still propose that API, making a difference between adapter
and utility lookup? What's the motivation? And would you deprecate plain
adapter calls and prefer 'adapt' all the time?
So as to prevent bikeshedding the API too much, I'm going to take your
+0.5 anyway. :)
Regards,
Martijn
More information about the Zope-Dev
mailing list