> Betreff: Re: [Zope-dev] Re: zcml filtering
> I'm +1 on zc.configuration.
> z3c.unconfigure, however, will contain zope.component
> specific code to "unconfigure" subscribers (which currently
> have no useful discriminator). So it's a hack to make it work
> with existing Zope code out there. If zope.component.zcml
> were changed to emit useful actions for <subscriber /> (and
> <interface />, too!), we could solely rely on shooting down
> actions and the code could find its way into
> zope.configuration. That will only help us with future Zope
> code, not with existing code out there (which this is for).
> Feel free to undertake this :)
That's a good argument but valid for any development or improvment
on existing code/packages.
The bad thing is that we now have 3 packages for one thing
I'm +1 too for a simple zope.configuration package which offers
the API for doing configuration how it should.
What do you think about to release z3c.unconfigure and merge it
to zope.configuration after the release. So we have both options
and a simple setup for the future.
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -