yuppie wrote:
I propose to move the Five bridging code (bridge.py,
fiveconfigure.createZope2Bridge and related tests) to the Interface
package of Zope 2. Five would still ship with a copy of that code for
Zope 2.7 backwards compatibility.
Based on a suggestion from philiKON and some
Lennart Regebro wrote:
On 7/6/05, yuppie [EMAIL PROTECTED] wrote:
Five comes with some code that bridges Zope 2 interfaces to Zope 3
interfaces. This way Zope 2 interface definitions can be reused without
adding redundant code.
This is quite useful, but doesn't work for Zope core interfaces:
On 7/6/05, yuppie [EMAIL PROTECTED] wrote:
Lennart Regebro wrote:
Did I understand that correctly, it is a problem if you want to use
Five *from* zope core code?
Correct. It's not always a problem, but the bridging code doesn't depend
on anything else in Five, so I guess moving that code
