I have isolated the problem with not providing tickets on runtime errors to
code the "callback" function of an ajax call.
If I modify the provided examples/controllers/ajax_examples.py with this
kind of error, and run it, I get the behavior. For example, this change to
the callback function "data" for the example does not give a ticket....
def data():
print "an error follows..."
msg=1+"hi"
if not session.m or len(session.m) == 10:
session.m = []
........(etc).......
For the time being I will debug my code by testing it with calls outside
ajax. I now have an avenue to more easily debug my code. Thank you for
your kind attention.
On Wednesday, October 10, 2012 1:08:26 PM UTC-4, Massimo Di Pierro wrote:
>
> I just tried and I do get a ticket.
>
> I think the problem is somewhere else. The only case I have found server
> may hang is if you have unbalanced {{...:}}....{{pass}} in your templates.
> Although I have not fully isolated the problem.
>
>
> On Wednesday, 10 October 2012 10:01:50 UTC-5, SallyG wrote:
>>
>> I'm having trouble debugging in web2py. If I introduce a python error
>> like:
>>
>> msg="hi"+909
>>
>> I don't get a "ticket" and the controller just stops at that point. Is
>> there a place I can find such runtime error messages?
>>
>> I'm running a new canned install on Ubuntu 12.04 (Version 2.0.9
>> (2012-09-13 23:51:30) stable). Thanks for any debugging aids you can point
>> out.
>>
>>
--
