Mark Ramm wrote: >> It should prolly be noted that the ini file is for deployment specific >> settings. Nothing so critical to the apps internal structuring should >> be in the ini.... like the template engine to use. > > Sure, that's fine and makes good sense. I will mention though that's > not what was done in tg, so it would be a change for our users.
It will not be much of a change IMO since the template language is declared in app.cfg which lives *inside* the egg (and is not modifiable, although overridabale :/, when deploying). As I see it, app.cfg is the "developers" config file while "prod.cfg" is the deployers. In this area I like Pylons' way of doing it better since leaving these kind of internal options open to be modified by the deployers is just asking for trouble. I think it's much better to hide these knobs well inside environment.py. Now digressing... we could discuss however what configuration system we want for TG2 (in turbogears-trunk probably). It could be feasible to use ConfigObj as TG 1.x does for something similar to app.cfg so we can move this "developers configuration" away from modules into config files. Not that I'm particularly advocating this route but maybe something worth considering. Alberto --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" 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/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
