On Apr 22, 2007, at 12:00 PM, Tres Seaver wrote:

I don't think this is necessary.  An egg that has ZCML should load
the ZCML from other eggs it depends on.  This means that these eggs
have to be designed this way.

Our override story is too weak to support this now, because the author
of package "C" may make a configuration choice which is inappropriate
for how "C" is used in "B" or "A":  we have no way to "turn off" such
choices (we can shadow them, but not disable them).  We really need a
way to spell "include the configuration from package 'A' except for the
view registrations" or "include only the utilitiy registration for the
'IFoo' utiltiy from package 'B'", or else we need to make the
configurations much more fine-grained.

Otherwise, we end up in a situation where using a package means
accepting all of its configuration blindly; at that point, there is no
win to moving the registrations out of Python code in the first place.

You argument is correct, however, in practice, it usually doesn't matter.

I would like to see a way to disable things in ZCML. There are a couple of proposals for doing this. I'd like to see one of them (preferably mind :) get implemented.


Jim Fulton                      mailto:[EMAIL PROTECTED]                Python 
CTO                             (540) 361-1714                  
Zope Corporation        http://www.zope.com             http://www.zope.org

Zope3-dev mailing list
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to