On Wed, Feb 11, 2009 at 9:02 AM, Mike Orr <[email protected]> wrote: > I personally validate and change the types of the config vars in > environment.py. That way if there's a missing or incorrect variable > it'll cause an error at startup rather than only in certain request > situations.
Makes great sense. > >> I didn't do any particular to be able to access the Pylons "config" >> object from my template, how does Pylons make it available for me? > > All the Pylons context variables are put in the template namespace > implicitly. c, app_globals (g), config, session, cache, url. And h > of course. It seems I don't have app_globals or g available in the template namespace, I had to use config["pylons.app_globals"] instead. Am I missing something? Thanks a lot, -- Eric --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
