Dieter Maurer wrote:
I, too, feel it is wrong
to use "implements(...)" when the class does not implement "...".
All declarations should be trustable -- otherwise, you could forget
about interfaces alltogether...
On some occasions you just can't fulfill an entire interface, and for
whatever reason can't or don't want to create a super interface that you
*can* fulfill so you do the best you can and raise NotImplemented when
you can't.
I don't know anything about this situation, so I don't know if that
approach is warranted here.
--
Benji York
Senior Software Engineer
Zope Corporation
_______________________________________________
Zope-Dev maillist - [email protected]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
