Make configuration file optional

Open dyangelo-grullon opened this issue 8 years ago • 1 comments

I find the current config setup to be pretty inflexible. I'd like to load configuration parameters from a database and provide the configuration parameters as kwargs. Should the constructor, for neat.Config, really take in the config file name? Should I make a PR to provide a convenience function that loads the parameters from the configuration file and converts it into a dict, so that users may pass the kwargs to the neat.Config constructor?

Oct 21 '17 18:10 dyangelo-grullon

I think it is essential to make configuration more general. Have you found a mature method to solve this problem?

Dec 13 '19 06:12 oushu1zhangxiangxuan1