Mmm, I know it is not the first time I am writing something boring about strange cron behavior on my Windows XP. Anyway, I post a summary here, so if someone happens to encounter same problem later, you will know you are not alone. :-)
In short, the cron.py 0.1.1 doesn't work on my pc, but cron.py 0.1.0 (from web2py 1.56.4 or earlier) can work, to some extend. I am using home edition 5.1.2600, Python 2.5.4, and a test app which uses cron feature. When using web2py_src.zip 1.59, 1.60.x, 1.61.1, the cron feature doesn't work at all. But if I use a cron.py 0.1.0 (from web2py 1.56.4) to OVERRIDE the cron.py 0.1.1 (web2py 1.61.1 build-in), the hardcron mode can work as expected. When using web2py_win.zip 1.61.1, by default cron doesn't work, either. But if I replace the cron.pyc inside library.zip to the cron 0.1.0 version, I can have a softcron feature. If I further replace the web2py.exe by another web2py.exe I build by myself (mentioned in my previous cron-relevent post), I get the hardcron. To Achipa: Since I have kind of workaround, I can live with current situation. If you need me to do further specific test, feel free to let me know. Regards, Iceberg --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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 -~----------~----~----~----~------~----~------~--~---
