Yeah, I was thinking that too, as a "I don't have time to think hard about
this" little daydream.
Actually I believe you would want to subclass InterfaceClass and make your new
zope.component.Interface an instance of the new InterfaceClass and specify
zope.interface's Interface as something it extends.
Then packages in the Zope world would start to use that Interface, I'd guess.
I don't know how I feel about it.
On Dec 17, 2009, at 11:51 AM, Chris McDonough wrote:
> I'll throw out the obvious...
> Why not subclass Interface in zope.component and make the required API
> additions there? If it were anybody but us thinking about doing this, they'd
> probably just subclass.
> - C
> Martijn Faassen wrote:
>> Wichert Akkerman wrote:
>>> Perhapse LookupError should be a subclass of TypeError.
>> It's a Python built-in. :)
>> Zope-Dev maillist - Zope-Dev@zope.org
>> ** No cross posts or HTML encoding! **
>> (Related lists -
>> https://mail.zope.org/mailman/listinfo/zope )
> Zope-Dev maillist - Zope-Dev@zope.org
> ** No cross posts or HTML encoding! **
> (Related lists -
> https://mail.zope.org/mailman/listinfo/zope )
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -