If dbg is the integrated web2py debugger, you could just open a new interaction window (debug button in admin) and then continue. Rocket should not block or stop, except you exhaust all threads. If you get an error message or any other issue, please send it to us so we can review it.
The more elegant way should be using breakpoints ;-) You can also pass a request.vars and enable set_trace only in that case. Best regards, Mariano Reingart http://www.sistemasagiles.com.ar http://reingart.blogspot.com On Fri, Feb 1, 2013 at 1:07 AM, Tim Richardson <[email protected]> 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. > > -- --- 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.
