Hi, Am Dienstag, den 10.07.2007, 22:49 +0300 schrieb 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.
It's not new, it's been there before and it does the same unclear thing as before. > 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? As Fred said, there's no need to do that. I actually thought about doing it the other way around: convert the new action objects into old-style actions. Christian _______________________________________________ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
