Possible for status to get stuck in executing during debugging.

[GoogleCodeExporter]

What steps will reproduce the problem?
1.  Ending program between status.executing=True and status.executing=False in 
CronScheduler.execute.  Can easily occur during debugging.

From then on the status is stuck in executing and no cron jobs will run.

Easy fix would be to set status.executing=False at the same time as all the old 
jobs are deleted 
during import of the module.

Original issue reported on code.google.com by benreyn...@gmail.com on 6 Jun 2009 at 4:10

[GoogleCodeExporter]

Good call... I'll add that in on my next commit :)

Original comment by Jim.mixt...@gmail.com on 11 Jun 2009 at 8:25

• Changed state: Accepted

[GoogleCodeExporter]

I have the same problem.

Original comment by fangzhou...@gmail.com on 12 Jun 2009 at 6:51

[GoogleCodeExporter]

I have this issue as well, I just didn't consider that people might use the same
database in development as they do on the live server, but it's definitely 
worth fixing!

Original comment by Jim.mixt...@gmail.com on 12 Jun 2009 at 12:32

• Changed state: Started