Next run information is incorrect about schedule HOT 3 CLOSED

@Toshibass are you sure that job was just run? If this message is printed right before the first run, it is perfectly valid.

from schedule.

Ok so here's another example ,,,
2015-10-17 09:57:04 - schedule - INFO - Running job Every 3 minutes do ESP_keep_alive() (last run: 2015-10-17 09:54:03, next run: 2015-10-17 09:57:03)

2015-10-17 09:57:04 - schedule - INFO - Running job Every 3 minutes do ESP_keep_alive()
yes its 09:57:04 so run the job.

(last run: 2015-10-17 09:54:03
yes for your information the last time the job ran was 09:54:03

next run: 2015-10-17 09:57:03) this time is 1 second in the past, surely the info should say the next time this schedule will run is 2015-10-17 10:00:03 then at that time..... you will see...

2015-10-17 10:00:04 - schedule - INFO - Running job Every 3 minutes do ESP_keep_alive() (last run: 2015-10-17 09:57:03, next run: 2015-10-17 10:03:04)

I guess the only time the original INFO makes sense is if you change "next run" to "this run" but that's not very useful information especially if the job is scheduled in days, surely this makes more sense, INFO its now xx running job, last time job ran was yesterday at xx, next time job will run is tomorrow at xx

Toshi

from schedule.

This has confused some people in the past. Let's include that discussion in #30.

Thanks for your question. Closing this so we can keep the tracker clean of loose ends. Feel free to follow up (or make a separate issue) with more questions/discussion 😃

from schedule.