FWIW I did finally get it working, to an extent.
I'm working on a Windows 7 machine to do this.
In one command tool window, I'm running my web2py application.
In another command tool window, I'm running the scheduler for my web2py
application.
In the model that contains the scheduled task that gets called I placed the
following two lines along with the import of rpdb2 elsewhere.
logger.debug('AWAITING DEBUGGER CONNECTION TO CONTINUE')
rpdb2.start_embedded_debugger("whatever")
Note that I comment these lines out when not needing the debugger.
I submit a job to the scheduled_task table.
When I see the 'AWAITING DEBUGGER CONNECTION TO CONTINUE' message in the
scheduler command tool window, I go to yet another command tool and start
winpdb and go through the attach.
This connects me to the proper process and I can step through it.
*NOTE: *You should change the timeout to the queue task call to something
like 600 seconds so that web2py doesn't think the process took too long to
run and reaps it while you're debugging.
--
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.
