schedule
schedule copied to clipboard
dbader
Python job scheduling for humans.
This is a re-open of #598 I schedule a daily job to run at a particular time in UTC. Most of the year the job runs at the correct local...
timezone_string = 'Europe/Berlin' This does not get run on a startup `schedule.every().day.at("13:05", timezone_string).do(day_rollover) ` Whereas this **runs on startup instantly** ` schedule.every().day.at("00:00", timezone_string).do(day_rollover) ` 2023-12-08 15:16:12,838 - INFO - Scheduler...
I have a feeling it's because I'm using multithreading, though I'm only using one schedule event. I don't really know what I'm doing wrong, but the event only runs once...
I am not sure whether you need to support all versions on python 3, but in case that yes, could you please consider something like ``` Index: schedule-1.1.0/test_schedule.py =================================================================== ---...
Sorry in advance if this is already documented somewhere, can't find it yet. I have functions that return values, and I'm struggling to see how to factor that into the...
```python def job(): global count logger.info("I'm doing a periodic job!" + str(count)) count = count + 1 time.sleep(30) # 每隔 2 分钟执行一次任务 job() schedule.every(2).minutes.do(job) while True: # logger.info("waiting for") schedule.run_pending()...
resolve #487 For some reason, pull request (#565) wasn't included in the release version, so I've set up a monthly schedule. Days 1 through 28 are supported, due to February's...
Add support for any kind of crontab expression #283 #491 For example : ``` schedule.every().crontab_expression("5 4 * * 2,5", "Europe/Amsterdam").do(job) ``` Largely inspired by Celery's https://github.com/celery/celery/blob/main/celery/schedules.py
This is more of a question than bug report, but this phenomenon has been confusing me for years. I guess a this is the appropriate place to ask about it....
