Am 20.03.2011, 18:07 Uhr, schrieb Tres Seaver <tsea...@palladion.com>:
> The one downside I can see is giving up on the sugar^Wexpressivity of > calling the interface directly -- I guess we could propagate the > 'default_factory' argument through to the '__call__' of interface. Note > that I *wanted* some extra sugar at one point (doing utility lookup when > no arguments were passed to Interface.__call__), but I haven't missed > that convenience much since I went on a low sugar diet with BFG / > pyramid. Callable interfaces are, in my view, a huge wart with a pimple on top! Convenient, yes, but just try and explain why a specification against which "living" code should be built should itself be executable. Charlie -- Charlie Clark Managing Director Clark Consulting & Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
