Thanks
On Friday, March 8, 2019 at 2:49:58 PM UTC+1, Anthony wrote:
>
> On Friday, March 8, 2019 at 4:55:02 AM UTC-5, icodk wrote:
>>
>> So if I understand it right, web2py caches compiled application files
>> and do it on the first demand or a source change and never write back to
>> storage/d
On Friday, March 8, 2019 at 4:55:02 AM UTC-5, icodk wrote:
>
> So if I understand it right, web2py caches compiled application files and
> do it on the first demand or a source change and never write back to
> storage/disk. If so, Is there any advantage for compiled web2py
> application (except
So if I understand it right, web2py caches compiled application files and
do it on the first demand or a source change and never write back to
storage/disk. If so, Is there any advantage for compiled web2py
application (except the one time load and compile after web server reset)?
On Friday, M
the web2py files gluon/*.py are compiled as you would expect and are in
gluon/*.pyc but, unlike flask or django where the user code imports the
framework, in web2py it is the framework that executes the user code (this
allows running multiple apps under one web2py). When web2py executes the
mo
4 matches
Mail list logo
