Hello,
I've just noticed[1] the adding of 'add_directive' method to 'Configurator'
which is allow to extend it with configuration methods. But I have some
questions:
1. Isn't this way is not very documentable? I mean, how would framework
extenders document methods, they've added to 'Configurator'? For example,
another solution to this problem is to compose application configurator from
pyramid.config.Configurator mixed with some other extension classes (Mix-in
pattern) -- this way extension methods are documented in their respectable
mix-ins in usual way. See how I've done in in contentlet[2].
2. I'm afraid this way does not respect ZCML mechanism of configuration, so
developers should bother both of adding methods to configurator and also of
adding corresponding ZCML directives. How about using some kind of reflection
to generate ZCML directives for new methods -- this way we can keep both
configuration API in sync?
[1]:
https://github.com/Pylons/pyramid/commit/659d5f6b1f7605daaa0666fab7061bba9848d241
[2]: http://packages.python.org/contentlet/#imperative-configuration
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com.
To unsubscribe from this group, send email to
pylons-devel+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/pylons-devel?hl=en.
