[Grok-dev] megrok.chameleon and (custom) template namespaces

Jan-Wijbrand Kolman janwijbrand at gmail.com
Mon Apr 18 07:11:41 EDT 2011

On 4/18/11 12:35 , Sylvain Viollon wrote:
> On Mon, 18 Apr 2011 12:01:08 +0200
> Jan-Wijbrand Kolman<janwijbrand at gmail.com>  wrote:
>    Hello,
>> This is one of these things that is very surprising to me: I always
>> thought and assumed and apparently never double-checked, that
>> templates are only reloaded when zope is running in "devmode on".
>> This is indeed not the case: whenever `__debug__` is True, the
>> template is reloaded.
>> Do people actually run their serves with `python -O` (which would
>> make `__debug__` False, but also would make assert statements to be
>> skipped)?
>    Honestly, I set CHAMELEON_DEBUG and CHAMELEON_SOURCE when I develop.
>    It works, and is good enough I think.
>    And as you can guess, I am totally against some Zope 3 specific
>    things inside megrok.chameleon.

Apart from the "zope 3 specificness" in this discussion:

I really do not like to have multiple flags and markers and environment 
variables for all kinds of configurations if we can have one: a flag 
that says whether the app is running in development-mode or not.

regards, jw

More information about the Grok-dev mailing list