cron is an addon, a contrib item that has been placed into web2py by default.
You might work on the core of web2py first - you can by default not start cron; in web2py.py, change the line: gluon.widget.start(cron=True) to read cron=False; Then you can start by focusing on the core of web2py first. On Sat, Aug 8, 2009 at 3:42 PM, holcomb <hol...@gmail.com> wrote: > > Commenting out signal import and call to signal in ln 806 of widget.py > brings the next error message of: > File "web2py.py", line 15, in web2py.py > File "c:\web2py\gluon\widgetpy.py", line 25, in c:\web2py\gluon > \widget.py > File "c:\web2py\gluon\contrib\cron.py", line 16, in c:\web2py\gluon > \contrib\cron.py > ImportError: No module named subprocess > > Moving on to cron.py, subprocess is also not in ipy b/c we don't have > to worry about GIL in .net. I'm going to try and replace the calls to > Popen\PIPE and see what happens and will report back. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
