Jorge Vargas schrieb: > I think we could somehow make the values auto transform, maybe call > paste's asbool, etc automagically?
Problematic. To be consequent, we will then have to evaluate all values (ints, lists) and require strings to be quoted. I also don't like the thought that config values will need to be evaluated *every* time you're accessing them. If you use ConfigObj, they are only evaluated once. >> It's inconvenient, error-prone and less performant if I need to evaluate >> or cast config options. And I don't see any methods for this, such as >> config.getint or config.getboolean that could be used in templates. >> > This could be very easy to add config is simply a Bunch object I think the original config parser has such methods. Maybe we need to proxy them or something. >> Therefore, in terms of usability, the new config system is a step back >> for me. >> > maybe but I find it a lot more useful and clean for the code base. I > think all of these are features we should grow into it. Can we make a > ticket? Ok, I'll summarize this in a ticket so we can rethink and improve the TG2 config system and the configurability of the templating system until the next release. I understand this is not easy to change because the config usage is so interwoven with Paste and Pylons - now the problems we had with the CherryPy 2 config are haunting us here as well. -- Christoph --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
