[tor-bugs] #9277 [BridgeDB]: BridgeDB's handling of config files is non-persistent and uses an old-style class

[Tor Bug Tracker & Wiki]

#9277: BridgeDB's handling of config files is non-persistent and uses an old-style
class
----------------------+-----------------------------------------------------
 Reporter:  isis      |          Owner:  isis
     Type:  defect    |         Status:  new 
 Priority:  normal    |      Milestone:      
Component:  BridgeDB  |        Version:      
 Keywords:            |         Parent:      
   Points:            |   Actualpoints:      
----------------------+-----------------------------------------------------
 Every time the process receives a SIGHUP, the configuration is reset to
 the settings within bridgedb.conf, which does not allow for methods within
 BridgeDB to make persistent configuration changes.

 The Main.Conf() class is also an old-style class which does not inherit
 from object(). This makes it difficult and buggy to subclass.

 The Conf.__getstate__() and Conf.__setstate__() methods do not exist, as
 with most other special methods, due to being an old-style class. The
 previous two methods make serialization impossible.

 Having proper support for congurable log levels in BridgeDB will require
 being able to make persistent config changes, otherwise the log level will
 just be continually reset to WARNING everytime a SIGHUP comes in.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9277>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online