-----BEGIN PGP SIGNED MESSAGE-----
Stephan Richter wrote:
> On Sunday 08 July 2007 13:19, Tres Seaver wrote:
>> I don't see how that can be: 'zope.event' hsa no dependencies, and
>> provides a service which is at least as low-level (lower, in my opinion)
>> as 'zope.schema': I can imagine *lots* of Zope3-based applications
>> which do not use zope.schema, but *none* which don't use zope.event,
>> zope.interface, and zope.component.
> z3c.rml does not use zope.component and thus clearly not zope.event.
I don't know why "clearly": 'zope.event' is a simple event channel
notification model, which has no dependency on components at all.
The application is free to do subscriptions in Python without any of the
rest of the architecture at all.
If anything, I would argue that schema's dependency on i18nmessageid is
a wart, at least as a hard dependency.
Using schema, but not component, has to be a one-percent case among
Zope3 applications, I would think. You likely don't even want
interface, in this case, since you aren't dispatching vies or adapters
against your schemas.
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope3-dev mailing list