> I don't think so. The old (TG1) config had only one type of config file
> (*.cfg instead of *.ini and *_cfg.py) and setting booleans and integers
> worked as expected. I can't remember having troubles with that system,
> while the new config system is immediately giving me headaches because
> booleans and integers are not evaluated in the *.ini files and the
> *_cfg.py files are just ugly and do not allow me to set arbitrary dotted
> config settings which is possible in the *.ini files.
Well, I was actually talking about the TG2 config system as it is now,
as compared to as it was a year ago when we were just using the pylons
system.
But I actually still think that the separation of python-style config
from the base ini files is a good thing, and I love ConfigObj but I
think that standard INI files work, and are well more standard
standard.
What is it about the app_cfg.py that you don't like specifically?
You can set any dotted config file reference you want using standard
python dictionary syntax:
base_config['pylons.foo']={'some":value}
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
