The current data structure for storing config options is a list initialized here.
But a dictionary would be more easily extendable if these config options change in the future, as some parts of the code would become independent wrt the number of config options (e.g. this line
Or perhaps even better: we could use something like configparser to store all config options in a .ini file and automatically populate such a dictionary at startup.
The current data structure for storing config options is a list initialized here.
But a dictionary would be more easily extendable if these config options change in the future, as some parts of the code would become independent wrt the number of config options (e.g. this line
Or perhaps even better: we could use something like configparser to store all config options in a
.ini
file and automatically populate such a dictionary at startup.