I just wanted to point out where we ended up wrt reusing
zope.configuration in Pyramid.
Pyramid uses zope.configuration internally to provide 2-phase
configuration and conflict detection; not just via ZCML but also via
imperative Python code. It uses the same included configuration is
overridden
Independent of my previous call for discussion about ZCML conflict
resolution, I'm cutting and pasting my side of a discussion about the
ZCML includeOverrides directive from an IRC chat, because it may come
in useful for folks grappling with its behavior. There's not really any
human-consumable
On Tue, Dec 7, 2010 at 1:57 PM, Chris McDonough chr...@plope.com wrote:
Independent of my previous call for discussion about ZCML conflict
resolution, I'm cutting and pasting my side of a discussion about the
ZCML includeOverrides directive from an IRC chat, because it may come
in useful for
On Tue, 2010-12-07 at 14:08 -0500, Jim Fulton wrote:
On Tue, Dec 7, 2010 at 1:57 PM, Chris McDonough chr...@plope.com wrote:
Independent of my previous call for discussion about ZCML conflict
resolution, I'm cutting and pasting my side of a discussion about the
ZCML includeOverrides
On 12/07/2010 12:27 PM, Chris McDonough wrote:
I *think* I'm of the opinion that libraries (or even reusable
applications) probably shouldn't need to use includeOverrides.
+1, I would be very suspicious of any library that uses
includeOverrides. Any use of it ought to be highly visible to
On Tue, Dec 7, 2010 at 2:27 PM, Chris McDonough chr...@plope.com wrote:
On Tue, 2010-12-07 at 14:08 -0500, Jim Fulton wrote:
On Tue, Dec 7, 2010 at 1:57 PM, Chris McDonough chr...@plope.com wrote:
Independent of my previous call for discussion about ZCML conflict
resolution, I'm cutting and
On Tue, 2010-12-07 at 14:27 -0500, Chris McDonough wrote:
[13:48] mcdonc override is exactly the wrong phrase to use in the name
of this directive
[13:51] mcdonc what it boils down to is that you never, ever really
want to use includeOverrides except in your rootmost zcml file
