Well, I've just checked in what I hope is the last little bit of config tweeking. Chris P. complained that pylons.config is not a Bunch, and while I'm not in favor of monkeypatching pylons to make that happen, I've created tg.config which acts like a bunch. Well, it actually does some more tricks in order to make attribute style access work in as many cases as possible.
The next bit that I'm working on will be getting dotted style lookup of templates back as an option for backwards compatability when using the new renderers, and getting some "full stack" tests going so we can test the transaction handling stuff, and the new renderers. Hopefully by then someone will have looked at the SecureResource ticket, if not, that will be the last thing on my list before the next alpha. If anybody wants to help out and do a quick bit of code review on tg.configuration, particularly the DictWrapper and get_partial_dict bits that I just added that would be awesome. The purpose of these two things is to make is so that you can write code like: config.pylons.request_options or config.app_conf.sqlalchemy and get back sensible results rather than having to get them with config['pylons.request_options'] or grapping all the sqlalchemy prefixed keys separately. config['app_conf]]['sqlalchemy.uri] config['app_conf]]['sqlalchemy.pool'] etc. As I type this up, I notice that there are a couple of unhanded edge cases in get_partial_dict which may require using a for loop rather than a generator expression. :( -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
