(typing too fast...)
On Thu, Mar 12, 2009 at 2:14 PM, Yarko Tymciurak <yark...@gmail.com> wrote:

>
> On Thu, Mar 12, 2009 at 1:35 PM, mdipierro <mdipie...@cs.depaul.edu>wrote:
>
>>
>> > I still remember the thread in this group referring to "an irritating
>> loss of code" due to timeouts...
>>
>> This does not happen any more. web2py editor has an ajax keepalive
>> since 1.57.
>>
>> Massimo
>>
>>
> and for the rest of the app - it needs to be up to the app writer.  You can
> set web2py instance timeout on the command like (see python web2py.py
> --help)
>

.... command line...

>
> The only thing I can possibly think of  (and it would be just a
> convenience) would be a command line way to set a global variable so that
> you could do something that looked like:
>
>    python web2py.py --command 'DEVEL=True'  -a '<recycle>'
>
> I think doing too much around development vs. deployment mode could get in
> the way more than hurt.
>

.... get in the way more than help....


>
> Even a way to insert a global is a convenience that might not be so useful
> - for example, if I have an app "my_app", and it uses a module, say
> "plugin_mymodule" --- I might want to set DEVEL for mymodule development,
> but NOT for my_app --- they are separate development activities....  in
> which case a global setting (as I show here, above) is not useful.
>
> Since each request reads the model area, you would need to set some
> models/0_development.py  with module "globals" like devel, and then the
> command line starts to resemble something like this:
>

.... like 0_devel.py...


>
>    python web2py.py --app-command '{"my_app" : "DEVEL=True"}' -a
> '<recycle>'
>
> and by now I would just rather set this manually in my app
>
> In other words, I don't think this is worth it.
>
> If you have some specific instance where you can show anything I've missed,
> I'd be grateful to see it.
>
> But for me, I just use an app level global in 0.py  DEVEL  and set it to
> True or False, and use it throughout my app.
>
> I have not been able to think of a better way to do this that gives the
> control that I want / need.   This convention for me also usefully separates
> this from the DEBUG variable (which I find better to keep separated).
>
> Hope this helps.
>
> Regards,
> Yarko
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to 
web2py+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to