On Sep 21, 2006, at 9:15 AM, Tres Seaver wrote:
I've wanted it. My major beef with the way we are *using* ZCML now is
that we expect package authors to provide policy-laden
their packages ("sensible defaults") but provide no means for the
to reuse that configuration selectively; their only realy choice
*copy* the configuration and edit it.
This is mostly true. I'll note that it is straightforward to
override things. It isn't straightforward to disable things,
Anyway, I think you raise a good point.
I argued *long* ago (after the first ZC-internal Zope3 sprint, I
that the '<include>' directive should be allowed to be complex, with
subelements like '<except>' or '<only>' to pull in specific
Such a practice would require either that we have XPath support
available, or else that we come up with a way to mark the directives
(e.g., a 'zcml:id' attribute).
I don't remember this, but I may have been focussed on other things.
I definitely think it would be good to have something like this. It
would be interesting to see some proposals with examples.
It would *also* require that we
implement the "no side-effects during parsing" policy (my other
"dead horse" in arguments about ZCML's implementation / usage).
Beat away. :) I've been in favor of this for some time. This is
definitely a goal.
Jim Fulton mailto:[EMAIL PROTECTED] Python
CTO (540) 361-1714
Zope Corporation http://www.zope.com http://www.zope.org
Zope3-dev mailing list