On Thu, Mar 04, 2010 at 11:19:52AM -0500, Benji York wrote: > On Thu, Mar 4, 2010 at 11:09 AM, Brian Sutherland > <br...@vanguardistas.net> wrote: > > On Thu, Mar 04, 2010 at 10:09:26AM -0500, Jim Fulton wrote: > >> In the specific case of zope.event, I'd prefer it stay separate. I > >> want developers to be able to publish events without having to commit > >> to a subscription mechanism. For example, ZODB depends on zope.event > >> so it can generate events and provide a generic hook mechanism. I > >> don't want it to depend on zope.component. > > > > I just committed a jinty-optional-event branch for zope.component that's > > an experiment as to how to make the dependency on zope.event optional. > > Maybe I'm missing something, but zope.event is so minimal I can't see > that making optional is worth the effort.
One point is backwards compatibility, the other is to allow zope.component subscribers to listen to ZODB events if the ZODB only depends on zope.event but not on zope.component. -- Brian Sutherland _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
