So does this mean compiled code (.py) is deployed or does it parse - generate etc.... on each instance startup and possibly cache generated code in the module ..... given you can't write to the filesystem.
T On Thu, Feb 4, 2010 at 10:35 AM, Chris McDonough <chr...@plope.com> wrote: > Hi Tim, > > AFAICT, as of 1.1 it "just works".. no need to distinguish between compile > time and runtime. I tested this last night. > > - C > > > On 2/3/10 8:50 PM, Tim Hoffman wrote: >> >> Hi Malthe >> >> Do you have a posting somewhere that details how one uses chameleon >> with appengine. >> I assume you are precompiling the template before deployment to appengine. >> >> But the only post I can find in repoze-dev talks about some strategies >> your where going to investigate. >> and I can't see anything in the docs specific. >> >> My guess is I use CHAMELEON_CACHE and then deploy its on disk cache of .py >> files >> >> Thanks >> >> T >> >> >> On Tue, Jan 26, 2010 at 7:42 PM, Malthe Borch<mbo...@gmail.com> wrote: >>> >>> 2010/1/26 Tim Hoffman<zutes...@gmail.com>: >>>> >>>> So whats the secret , pre-compile everything ? >>> >>> Same procedure as last year, except we now use the compilation hoops >>> from Genshi which makes it work, plus some rewrites of our code >>> transformation logic. >>> >>> \malthe >>> >> _______________________________________________ >> Repoze-dev mailing list >> Repoze-dev@lists.repoze.org >> http://lists.repoze.org/listinfo/repoze-dev >> > > > -- > The repoze.bfg Web Application Framework Book: http://bfg.repoze.org/book > _______________________________________________ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
