Re: [Repoze-dev] Separate 'compile' and 'execute' steps in Chameleon [was: Re: repoze.bfg trunk "C-free"]

2009-05-04 Thread Hanno Schlichting
Malthe Borch wrote: > 2009/5/4 Carlos de la Guardia : >> If Malthe or anyone else has a good idea about how to do this and will give >> me some pointers, I'm willing to use my limited abilities to make this work. >> Otherwise, I might try to bring in old zpt. > > It can be done, but it requires th

Re: [Repoze-dev] Separate 'compile' and 'execute' steps in Chameleon [was: Re: repoze.bfg trunk "C-free"]

2009-05-04 Thread Malthe Borch
2009/5/4 Carlos de la Guardia : > If Malthe or anyone else has a good idea about how to do this and will give > me some pointers, I'm willing to use my limited abilities to make this work. > Otherwise, I might try to bring in old zpt. It can be done, but it requires the introduction of a new compi

Re: [Repoze-dev] Separate 'compile' and 'execute' steps in Chameleon [was: Re: repoze.bfg trunk "C-free"]

2009-05-03 Thread Carlos de la Guardia
I tried a separate compile step yesterday, but chameleon uses marshal for recreating the code objects from the .cache files. It also uses compiler and ast to generate the compiled templates that are stored in a registry once the app is running. Compiler is OK until it tries to use parser, which is

Re: [Repoze-dev] Separate 'compile' and 'execute' steps in Chameleon [was: Re: repoze.bfg trunk "C-free"]

2009-05-03 Thread Chris McDonough
On 5/3/09 8:51 PM, Sidnei da Silva wrote: > On Sat, May 2, 2009 at 1:53 PM, Carlos de la Guardia > 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

[Repoze-dev] Separate 'compile' and 'execute' steps in Chameleon [was: Re: repoze.bfg trunk "C-free"]

2009-05-03 Thread Sidnei da Silva
On Sat, May 2, 2009 at 1:53 PM, Carlos de la Guardia 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