The bug is related to a new api for python-configobj : New in ConfigObj 4.7.0: It is no longer possible to instantiate ConfigObj with an options dictionary as in earlier versions. To modify code that used to do this simply unpack the dictionary in the constructor call: config = ConfigObj(filename, **options)
So simply adding ** before dicts in blueproximity.py fixes the issue. See attached patch.
--- proximity.py 2008-02-28 16:59:01.000000000 +0100
+++ proximity.py.new 2010-02-07 11:00:57.332505830 +0100
# system includes
@@ -377,7 +377,7 @@
pass
# then let's get it on...
# create the new config
- newconf = ConfigObj(self.config.dict())
+ newconf = ConfigObj(**self.config.dict())
newconf.filename = newname
# and save it to the new name
newconf.write()
@@ -1257,7 +1257,7 @@
if filename.endswith('.conf'):
try:
# add every valid .conf file to the array of configs
- config = ConfigObj(os.path.join(conf_dir,filename),{'create_empty':False,'file_error':True,'configspec':conf_specs})
+ config = ConfigObj(os.path.join(conf_dir,filename),**{'create_empty':False,'file_error':True,'configspec':conf_specs})
# first validate it
config.validate(vdt, copy=True)
# rewrite it in a secure manner
@@ -1271,7 +1271,7 @@
# no previous configuration could be found so let's create a new one
if new_config:
- config = ConfigObj(os.path.join(conf_dir, _('standard') + '.conf'),{'create_empty':True,'file_error':False,'configspec':conf_specs})
+ config = ConfigObj(os.path.join(conf_dir, _('standard') + '.conf'),**{'create_empty':True,'file_error':False,'configspec':conf_specs})
# next line fixes a problem with creating empty strings in default values for configobj
config['device_mac'] = ''
config.validate(vdt, copy=True)
signature.asc
Description: OpenPGP digital signature
