[Product-Developers] RFC: Venusian-based Python-syntax alternative for ZCML-configuration
steve at dcn.org
Sat Jan 4 22:22:08 UTC 2014
I like this a lot. It allows us to get configuration into Python without
being as magical as grok.
One thing I particularly like: knowledge of zcml would easily map to this
-- and back! That would make it great for teaching.
On Fri, Jan 3, 2014 at 12:17 AM, Asko Soukka <asko.soukka at iki.fi> wrote:
> last year there was (again) a long discussion about pros and cons of
> grok-based configuration:
> TL;DR; It seems that Grok will never have feature parity with ZCML, but it
> has use cases and we have nothing to replace it.
> I've been experimenting with an alternative lately: a venusian-based
> configuration library for zope.configuration; All python, minimal
> dependencies, uses the same directive code as ZCML (= feature parity), no
> conventions - just IDE-friendly Python-based configuration.
> I'm not forcing this to anyone. An another way to configure may be the
> last thing we need. Yet, I want to try this approach as a grok-replacement
> for our (my employer) internal packages during this spring (we'll have new
> developers and grok has always been easier to teach than ZCML). Only for
> So, before spending too much time polishing the code, I'd like to request
> for your comments about the configuration syntax, which I've been tinkering:
> So, it's not grok. It's a Python-syntax for zope.configuration with
> optional support for limited set of decorators (directives with class,
> factory or handler).
> Venusian-library is used to make all configuration directives lazy:
> venusian creates "registration callbacks" during module import, but those
> callbacks are only executed when packages is imported by zope.configuration.
> The current catch is that this needs one line in zope.conf (for
> monkeypatching zope.configuration) and custom site.zcml (for
> z3c.autoinclude also Python-configured packages). These are required to
> work around hardcoded zcml-expectations.
> Waiting for your comments.
> Product-Developers mailing list
> Product-Developers at lists.plone.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Product-Developers