HI Chris
Sunday morning, forgot to reply-all
sorry
Will forward the other emails now
T
On Sun, May 10, 2009 at 9:29 AM, Chris McDonough wrote:
> On 5/9/09 9:10 PM, Tim Hoffman wrote:
>>
>> The more I think/understand the way chameleon works the less likely I
>> think it is going to work.
>>
>
Tres Seaver wrote:
> Hanno Schlichting wrote:
>> Only having pyc files is also a pain with zope.testing and its eager
>> cleanup mode, which would constantly delete these files.
>
> I think the "keep .pyc files" mode is only for deployment (to GAE or
> other platforms which can't compile the templ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
> Chris McDonough wrote:
>> On 5/9/09 9:12 AM, Martin Aspeli wrote:
>>> It'd be nice if there was a way to name the files that meant people
>>> won't accidentally commit a bunch of "compiled" .py files that may then
>>> end up
2009/5/9 Hanno Schlichting :
> Do we really need to be able to switch this mode via CHAMELEON_STATIC?
> I'd be tempted to make the static mode the default and not have it
> configurable. The whole compilation process is already quite complicated
> and I wouldn't want to increase this by adding more
Malthe Borch wrote:
> As a general improvement (in terms of clarity) and as part of the
> efforts of getting Chameleon working on GAE, I've begun reworking the
> compilation stage.
Yeah!
> 3) If the ``CHAMELEON_STATIC`` flag is enabled, compile into
> one-method-fits-all-arguments render methods
Chris McDonough wrote:
> On 5/9/09 9:12 AM, Martin Aspeli wrote:
>> It'd be nice if there was a way to name the files that meant people
>> won't accidentally commit a bunch of "compiled" .py files that may then
>> end up conflicting later.
>
> Maybe there could be a mode to compile template files
On 5/9/09 9:12 AM, Martin Aspeli wrote:
> Chris McDonough wrote:
>> On 5/9/09 8:50 AM, Malthe Borch wrote:
>>> As a general improvement (in terms of clarity) and as part of the
>>> efforts of getting Chameleon working on GAE, I've begun reworking the
>>> compilation stage.
>>>
>>> If not explicitly
2009/5/9 Martin Aspeli :
> We can't go straight to .pyc? Won't GAE execute .pyc files?
Who knows. By the way, can someone confirm if the GAE supports the
``execfile`` built-in? It doesn't seem to provide the ``imp`` module
which we currently use to load and compile template source code.
> Also se
Chris McDonough wrote:
> On 5/9/09 8:50 AM, Malthe Borch wrote:
>> As a general improvement (in terms of clarity) and as part of the
>> efforts of getting Chameleon working on GAE, I've begun reworking the
>> compilation stage.
>>
>> If not explicitly disabled (using ``CHAMELEON_CACHE=0``), templat
On 5/9/09 8:50 AM, Malthe Borch wrote:
> As a general improvement (in terms of clarity) and as part of the
> efforts of getting Chameleon working on GAE, I've begun reworking the
> compilation stage.
>
> If not explicitly disabled (using ``CHAMELEON_CACHE=0``), template
> files (ending in .pt) will
As a general improvement (in terms of clarity) and as part of the
efforts of getting Chameleon working on GAE, I've begun reworking the
compilation stage.
If not explicitly disabled (using ``CHAMELEON_CACHE=0``), template
files (ending in .pt) will be compiled with the result written to a
Python-m
11 matches
Mail list logo
