From d6b72d90e658140961b040e53c009d82fa0f11c9 Mon Sep 17 00:00:00 2001 Message-Id: From: Mark Wooding Date: Sat, 16 Mar 2013 00:31:03 +0000 Subject: [PATCH] operation.py: Refactor `polswitch' a little. Organization: Straylight/Edgeware From: Mark Wooding We're going to use this structure again. --- operation.py | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/operation.py b/operation.py index 1184e3d..e10a1b5 100644 --- a/operation.py +++ b/operation.py @@ -40,6 +40,16 @@ import util as U ### semantics may be that the services are all assigned the /same/ random ### password.) +###-------------------------------------------------------------------------- +### Some utilities. + +OPS = ['set', 'reset', 'clear'] +## A list of the available operations. + +class polswitch (U.struct): + """A small structure holding a value for each operation.""" + __slots__ = OPS + ###-------------------------------------------------------------------------- ### Operation protocol. @@ -243,14 +253,11 @@ CONF.export('ClearRequest') ###-------------------------------------------------------------------------- ### Master policy switch. -class polswitch (U.struct): - __slots__ = ['set', 'reset', 'clear'] - CONF.DEFAULTS.update( ## Map a request type `set', `reset', or `clear', to the appropriate ## request class. - RQCLASS = polswitch(None, None, None), + RQCLASS = polswitch(**dict((i, None) for i in OPS)), ## Alternatively, set this to a mixin class to apply common policy to all ## the kinds of requests. -- [mdw]