On Tue, Feb 24, 2009 at 10:38 AM, Christoph Zwerschke <[email protected]> wrote: > > The config system of TG2 is separated into *.ini config files and > *_cfg.py" files in the config directory. > > The idea is that deployment specific settings should go to the *.ini > files and application specific settings to the *_cfg.py files and that > the deployer should have an easy life with *.ini files while the > application developer can be burdened with py code files. > > However, I don't think it's only the application developer who wants to > customize the applications settings; otherwise he could have hard coded > these settings. The deployer may just as well want to change certain > application settings. > > So I think there should be another *.ini file for application specific > settings. The *_cfg.py file is really ugly with all of these repetitions > of "base_config.". Any chance that this gets improved in 2.1?
Funny I now find the .ini stuff ugly and the .py stuff awesome having configuration values on how the app is loaded in python is great, in fact I though we'll eventually face out the .ini file to leave only the absolutely necessary stuff in there, and simply move things to the python files. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
