On Fri, Jul 12, 2013 at 3:19 PM, Moritz Schlarb <[email protected]>wrote:
> Since I struggled with that lately, too, I appreciate all kind of > improvement, although I now know my way around :D > > My 2 cents atm: > > Why is it strictly required for @expose to know about the renderers? > Couldn't that be done more lazy when they are first used? > > Up to now I have actually two branches on my local repo that try to do that, but both of them don't satisfy me due to various reasons. I'll give a third try, I have an idea for a more flexible solution and that should not slow down too much things, but it won't go in 2.3 stable as it is too big change between a beta and a stable. > For init_config, there was one thing that helped me a lot after having no > success, and we should definitely document it somewhere: > In any hook, or in after_init_config, or really anywhere, it can be very > helpful to import tg.config as tgconf in the scope of the function and not > globally in app_cfg.py! > > That is another thing that confuses people a lot. Both base_config and tg.config contain configuration options, but they do it partially and at different times. I think we should at least document the proper way to do that. Sooner or later some refactoring to make it more clear will be required. -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/turbogears-trunk. For more options, visit https://groups.google.com/groups/opt_out.
