[Zope3-dev] Proposal: Make zope.configuration actions better re-usable

[Marius Gedminas]

On Tue, Jul 10, 2007 at 12:48:42PM +0200, Christian Theune wrote:
> Please see
> https://blueprints.edge.launchpad.net/zope3/+spec/reusable-configuration-actions
> 
> Discussion on this thread :)

I like it.  +1

The semantics of the new 'order' attribue are a bit unclear.

What's the migration plan for old-style actions?  Will
IConfigurationContext.action() use something like

  class OldStyleConfigurationAction(object):

      implements(IConfigurationAction)

      def __init__(self, discriminator, callable, args, order=0):
          self.discriminator = discriminator
          self.order = order
          self.callable = callable
          self.args = args

      def __call__(self):
          self.callable(*self.args)

in addition to emitting a deprecation warning, perhaps?

Marius Gedminas
-- 
If you sat a monkey down in front of a keyboard, the first thing typed would be
a unix command.
                -- Bill Lye
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://mail.zope.org/pipermail/zope3-dev/attachments/20070710/7c95868b/attachment.bin