it's a "general issue" with debugging remote processing http://pydev.org/manual_adv_remote_debugger.html
BTW: if you launch the function in the shell, you won't have access to the inner workings of the scheduler but you'll see what our function/module/etc is doing.... the env in which tasks are executed within the scheduler is pretty much the same of web2py's shell with models loaded (./web2py.py -M -S appname). On Wednesday, July 23, 2014 3:44:13 PM UTC+2, Stephen Weiss wrote: > > I want to use a debugger (winpdb) to step through a scheduler module. > > However, when I run the scheduler in the debugger (-K option) and I set a > breakpoint in my module and submit a job to the scheduler_task table, > I get debug output (prints) in the console, but the breakpoint is never > hit. The row in the scheduler_task table changes to COMPLETED. > > Thus, I know the scheduler is running my module in the debugger, but it > just won't stop at the breakpoint I have set. > > I believe the issue is with the multi-threaded nature of the scheduler and > debugger, but I don't know how to resolve the problem. > > Any help would be greatly appreciated. > > Thanks! > > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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/d/optout.
