Belated response, but..

Jim Fulton wrote:
> Speaking of Zope 2.8, Jeremy Hylton has suggested that, perhaps, Zope 2.8
> should be a release that provides *only*:
> - New-style ExtensionClass, and
> - ZODB 3.3, featuring multi-version concurrency control,
> plus any features that have been added to the head since the Zope 2.7
> branch was created.

If this hasn't been added to the head yet, being able to use Zope 3
interfaces on Zope 2 objects would be nice. Right now Zope barfs
over any class that gets registered that uses Zope 3 interfaces.

That way the Zope 3 interfaces and component architecture packages
can be used from Zope 2, at least to a certain extent.

One fairly simple way around that is to modify Zope 3 interfaces so
they don't use __implements__ but something else (I used __implements2__)
but that could be seen as a hack. It is clean in the sense that Zope 2
won't trip over Zope 3 and vice versa.

But perhaps there's another approach which actually modifies the Zope 2

> This idea is pretty appealing to me.  I wonder what others think of it.

If it also has the interfaces matter sorted out and it causes this to
be released more quickly, then by all means.

It's easy enough for me to include other parts of the Zope 3 source tree.



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

Reply via email to