dbg is the integrated web2py debugger in this case. The behaviour I observe is that rocket no longer reponds: I can't retrospectively open an admin session. I get no error tickets although maybe something is logged somewhere. I think it affects all users. This is running on windows, latest stable. I'll check more thoroughly and if I'm correct and if I can reproduce it, I'll file a report.
On Friday, 1 February 2013 15:07:16 UTC+11, Tim Richardson wrote: > > I use dbg.set_trace for debugging. > Usually I remember to run an instance of web2py on an additional port and > use that for my debugging. > Sometime I forget to remove dbg.set_trace. > When I do that, I don't have a listening window open, so I guess rocket > stops but there is no one to hear it. > I'm on Windows. > When this happens, the server stops responding to all requests. I restart > the Windows service (which is basically python web2py.py) > > Is there a more elegant way of dealing with this situation? > > > -- --- 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.
