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 eleg
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
2 matches
Mail list logo
