On 5/3/09 8:51 PM, Sidnei da Silva wrote:
> On Sat, May 2, 2009 at 1:53 PM, Carlos de la Guardia
> <carlos.delaguar...@gmail.com>  wrote:
>> Chameleon.* will not work because it needs to generate code objects and
>> that's forbidden in GAE (no marshal.py, parser.py or direct calls to
>> new.code() or similar).
> I would like to bring up an idea that Paul Everitt had:
> - What if chameleon supported separate 'compile' and 'execute' steps?
> 1. Chameleon basically compile templates to Python source code.
> 2. It is possible to save the generated source code to .py files
> (CHAMELEON_SOURCE or something in the environment)
> 3. Therefore, it should be possible to copy the .py files to GAE and
> have them be executed without recompiling from the .pt file (of course
> with some changes to chameleon)

IIRC, the "cache" files in Chameleon aren't just .py files, they hold a 
marshalled code object plus other info in the pickle that Chameleon uses to 
resolve macros (I think).  I suspect it's not falling-off-a-log easy as a 

- C
Repoze-dev mailing list

Reply via email to