Issue5 Editing

TitleWrapping Zope2 Interfaces
Priorityfeature Statusin-progress
Superseder Nosy Listtseaver, faassen
Assigned Totseaver TopicsFive

Created on 2004-08-02.05:08:52 by tseaver, last changed 2004-08-27.15:37:44.

Messages
msg15 Author: faassen Date: 2004-08-27.15:37:44 remove
Do you think the recent mails about how to get the tests to
work will help you get unstuck again? :)
msg14 Author: tseaver Date: 2004-08-27.13:39:45 remove
Martijn Faassen wrote:
> Martijn Faassen <faassen@infrae.com> added the comment:
> 
> Tres, this only needs to be merged, right?

Yep.  I got stuck on unit testing issues and thus didn't feel able to do 
the merge myself.

Tres.
msg13 Author: faassen Date: 2004-08-27.10:39:18 remove
Tres, this only needs to be merged, right?
msg9 Author: tseaver Date: 2004-08-02.05:08:52 remove
I have rolled a 'utilities.py' module for creating Zope3
interfaces from Zope2 interfaces;  the theory is that the
existing Zope3 interfaces (and corresponding __implements__)
machinery can't be changed, but I'd like to reuse the APIs
in Five.

I am currently doing the wrapping in a Python module, e.g.::

  from utilities import fromZ2Interface
  from Products.CMFCore.interfaces.CachingPolicyManager \
    import CachingPolicyManager as _IZ2_CachingPolicyManager
 
  ICachingPolicyManager =
fromZ2Interface(_IZ2_CachingPolicyManager)
 
  del _IZ2_CachingPolicyManager

However, this is noisy and boilerplate-filled;  I would
prefer to be able to do this effort in ZCML.

Is the notion interesting to Five as a project?
History
Date User Action Args
2004-08-27 15:37:44faassensetmessages: + msg15
2004-08-27 13:39:46tseaversetmessages: + msg14
2004-08-27 10:39:25faassensetnosy: + faassen
2004-08-27 10:39:18faassensetmessages: + msg13
2004-08-27 10:38:34faassensetassignedto: (no value)
2004-08-27 10:38:01faassensetstatus: unread
2004-08-02 05:08:52tseavercreate