2013/2/26 Niphlod <[email protected]>: > 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 [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.
