uhm ... all the "logic" should then take place in the "def console()" on 
the gluon/widget.py file .... 

there's no "profiling" available but if you add a few prints here and there 
you should get a general idea on who's spending that much time around

On Tuesday, April 23, 2013 3:10:10 PM UTC+2, Reza Shah wrote:
>
> Yes, i started with -a and tried -i option too.
>
> On Tuesday, April 23, 2013 9:58:57 PM UTC+9, Niphlod wrote:
>>
>> are you starting it with web2py.py -a 'password' ? (if -a is passed no 
>> GUI is istantiated --> narrows down the possibilities)
>>
>> On Tuesday, April 23, 2013 2:32:33 PM UTC+2, Reza Shah wrote:
>>>
>>> How to find out which part of web2py takes time(if possible)?
>>> I tried running with --verbose but i didnot see any verbose message.
>>>
>>> On Tuesday, April 23, 2013 9:12:03 PM UTC+9, Niphlod wrote:
>>>>
>>>> not at all .... 2-3 seconds at best is what it takes from web2py.py -a 
>>>> yourpassword to the "use kill SIGTERM blablabla"
>>>>
>>>>
>>>>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to