I have a complicated class hierarchy in which the classes are similar to each other but every class contains a bunch of more or less complicated stateful variables. To give you an impression, please have a look at this minimal working example:
class OptVar:
"""
Complicated stateful variable
"""
def __init__(self, **kwargs):
self.parameters = kwargs
class OptVarContainer:
"""
Class which contains several OptVar objects and nested OptVarContainer
classes. Is responsible for OptVar management of its sub-OptVarContainers
with their respective OptVar objects.
"""
def __init__(self, **kwargs):
for (key, value_dict) in kwargs.items():
setattr(self, key, OptVar(**value_dict))
class C(OptVarContainer):
"""
Specific implementation of class OptVarContainer
"""
def __init__(self):
super(C, self).__init__(
**{"my_c_a": {"c1": 1, "c2": 2},
"my_c_b": {"c3": 3, "c4": 4}})
class B(OptVarContainer):
"""
Specific implementation of class OptVarContainer
"""
def __init__(self):
super(B, self).__init__(**{"b": {"1": 1, "2": 2}})
self.c_obj = C()
class A(OptVarContainer):
"""
Specific implementation of class OptVarContainer
"""
def __init__(self):
super(A, self).__init__(
**{"a1": {"1": 1, "2": 2},
"a2": {"a": "a", "b": "b"}})
self.b_obj = B()
def main():
# creating OptVarContainer with some nested OptVarContainers.
my_a_obj = A()
# It is intended behaviour to access the OptVar objects via
# scoping within the class hierarchy.
print(my_a_obj.b_obj.b.parameters)
my_a_obj.b_obj.b.parameters["2"] = 3
print(my_a_obj.b_obj.b.parameters)
print(my_a_obj.b_obj.c_obj.my_c_a.parameters["c1"])
my_a_obj.b_obj.c_obj.my_c_a.parameters["c1"] = 6
print(my_a_obj.b_obj.c_obj.my_c_a.parameters)
# Two major problems:
# a) Serialization (with compatibility between different versions)
# b) Access to all OptVar objects at once
if __name__ == "__main__":
main()
The question is now: How to access the OptVar objects the best. I already thought about to use some kind of pool object and use some proxy within the class hierarchy to have a link to the pool. This pool should not be a singleton, since it should be possible to manage more than one pool at a time. Up to now the access to the OptVar variables within my own code are via some Python black magic and tranversing the classes in an recursive manner avoiding infinite loops by maintaining an id list. This is quite ugly and only considered temporary.
I am aware that no unique solutions exist for this design problem, but I need further input on that from you.
The full context of this question is here but after some discussions I separated the design part.
Aucun commentaire:
Enregistrer un commentaire