For future reference just adding the fact that you can open a web2py shell
and call your scheduler tasks directly in order to debug them. This wasn't
obvious to me but is much easier than trying to run the scheduler and debug
it via logging statements.
For example:
python web2py.py -M -S your_app_name
and then call a function from your scheduler.py file which will just be a
global function (that is, just type the function name at the shell
prompt). Inside your function you can set a pdb break point and debug to
your heart's content.
scheduler.py:
def myfunction():
import pdb; pdb.set_trace()
...
On Wednesday, February 27, 2013 4:36:10 PM UTC-5, José L. wrote:
> 2013/2/26 Niphlod <nip...@gmail.com <javascript:>>:
> > never done it, but debugging a multiprocessing spawned process needs
> > additional tuning http://pydev.org/manual_adv_remote_debugger.html
> >
> > PS: can I ask what is not working ? if it's a "focused" problem maybe I
> can
> > come up with an answer .
>
> I've fixed it , it was a problem with a locked file when using shelve.
> I've used a workaround but I don't feel happy with the solution (it
> works but's terribly ugly). Any idea to exchange a big Python list
> with data between the main web2py application and the long-lasting
> backgroud process is welcome.
>
> Regards.
>
>
> >
> >
> > On Tuesday, February 26, 2013 9:12:23 PM UTC+1, José L. wrote:
> >>
> >> Hello,
> >> I'm working with async processes using the scheduler (with the
> >> unvaluable help of the "learn by trial" application from Niphlod.
> >>
> >> I wonder if there's an easy way to debug the processes that are being
> >> executed in the background (I'm having problems with them, they work
> >> ok when run from web2py directly as a normal process, but not when
> >> they're executed by the scheduler).
> >> Pdb would be great, but if not, is there any way to use the ugly but
> >> useful "print vars" commands to see the flow of execution of the
> >> tasks?
> >>
> >> I know of the output field in the scheduler_task table in the
> >> database, but that's terribly slow....
> >>
> >> Regards.
> >> José L.
> >
> > --
> >
> > ---
> > 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 web2py+un...@googlegroups.com <javascript:>.
> > For more options, visit https://groups.google.com/groups/opt_out.
> >
> >
>
--
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 web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
