I had a closer look at Zope 2.8's Five and I'm concerned about the fact that Five ships with redundant interface definitions:

- redundant code is always a problem because it's hard to keep things in sync

- the fact that Five is maintained in a different repository and should work with different Zope versions makes it almost impossible to change Zope interfaces in a consistent way

So my questions are:

1.) Why are interfaces that are available as Zope 2 interfaces duplicated in Five/interfaces.py instead of bridged?

2.) Could we move the interfaces that are currently not available as Zope 2 interfaces to the corresponding packages in Zope 2.8, using Five/interfaces.py just as an fallback for Zope 2.7 and old Five products?

If people agree that this is problem, I'd volunteer to help resolving it.



Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )

Reply via email to