summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDenis Laxalde <denis.laxalde@logilab.fr>2017-07-05 16:36:37 +0200
committerDenis Laxalde <denis.laxalde@logilab.fr>2017-07-05 16:36:37 +0200
commit57c1a89bc7ef582a85f291c976c932c59062a1ce (patch)
tree84796810370381d6ed7e52e97baf7017eeb7d54d
parent40beb6d5fc958a17ac7a0b043d1a34409b6c7e42 (diff)
downloadlogilab-common-57c1a89bc7ef582a85f291c976c932c59062a1ce.tar.gz
configuration: fix action query in read_old_config
From the context, using action[0] seems correct. The problem comes from changeset 0a22ff6e5207 and shows up when using "option_added()" CubicWeb migration command.
-rw-r--r--logilab/common/configuration.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/logilab/common/configuration.py b/logilab/common/configuration.py
index 52ac6df..9c23525 100644
--- a/logilab/common/configuration.py
+++ b/logilab/common/configuration.py
@@ -1045,7 +1045,7 @@ def read_old_config(newconfig, changes, configfile):
option, oldtype, newvalue = action[1:]
changesindex.setdefault(option, []).append((action[0], oldtype, newvalue))
continue
- if action[1] in ('added', 'removed'):
+ if action[0] in ('added', 'removed'):
continue # nothing to do here
raise Exception('unknown change %s' % action[0])
# build a config object able to read the old config