The current scheduler in py4web only has the concept of task_runs
In web2py there was a separation between a task and its runs
The separation of tasks and runs in web2py made it easy to manage tasks, specially periodic tasks.
In py4web, if I schedule a periodic task:
1) A new run of the task will only be executed when the previous run has completed
2) How to change the period of a scheduled task? Stop the current running instance and start a new schedule?
3) If the scheduler is stopped for whatever reason, the periodic task becomes 'dead' and no new instances are scheduled.
Are there any plans to evolve the scheduler in py4web (more towards the one that exists in web2py)?