The scheduler dosen't stop at end_time #814
-
|
I'm trying to schedule a task to run each 10 seconds until the specified import logging
import pytz
from apscheduler import Scheduler
from apscheduler.triggers.cron import CronTrigger
from datetime import datetime, timedelta, timezone
logging.basicConfig()
logging.getLogger('apscheduler').setLevel(logging.DEBUG)
def fn():
tm = datetime.now().strftime('%H:%M:%S')
print(tm)
with Scheduler() as scheduler:
d = datetime.now() + timedelta(seconds=20)
end_time = d.astimezone(pytz.timezone('Europe/Paris'))
scheduler.add_schedule(fn,
CronTrigger(second='0, 10, 20, 30, 40, 50', end_time=end_time),
misfire_grace_time=None,
max_running_jobs=1)
scheduler.run_until_stopped()And here is the log: I'm using v4.0.0a3. This is true for the asynchronous version as well. Is there anything I misunderstood? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 13 replies
-
|
It's supposed to stop running the schedule after |
Beta Was this translation helpful? Give feedback.
-
|
Where and how can I stop it? Do I have to check the current time versus the |
Beta Was this translation helpful? Give feedback.
-
import logging
from backports.zoneinfo import ZoneInfo
from apscheduler import Scheduler, ScheduleRemoved
from apscheduler.triggers.cron import CronTrigger
from datetime import datetime, timedelta, timezone
logging.basicConfig()
logging.getLogger('apscheduler').setLevel(logging.DEBUG)
def fn():
tm = datetime.now().strftime('%H:%M:%S')
print(tm)
def listener(event: ScheduleRemoved):
scheduler.stop()
with Scheduler() as scheduler:
d = datetime.now() + timedelta(seconds=20)
end_time = d.astimezone(ZoneInfo('Europe/Paris'))
scheduler.add_schedule(fn,
CronTrigger(second='0, 10, 20, 30, 40, 50', end_time=end_time),
misfire_grace_time=None,
max_running_jobs=1)
scheduler.subscribe(listener, {ScheduleRemoved})
scheduler.run_until_stopped() |
Beta Was this translation helpful? Give feedback.
-
|
Because of an unknown issue, I can't install I'm using v4.0.0a3. |
Beta Was this translation helpful? Give feedback.
-
|
Hmm...this looks like a bug in the synchronous scheduler interface. It worked for me because I had already fixed this locally. This will be rectified in the next release. For now, you can patch the method locally: import logging
from zoneinfo import ZoneInfo
from functools import partial
from apscheduler import Scheduler, ScheduleRemoved
from apscheduler.triggers.cron import CronTrigger
from datetime import datetime, timedelta, timezone
logging.basicConfig()
logging.getLogger('apscheduler').setLevel(logging.DEBUG)
def fn():
tm = datetime.now().strftime('%H:%M:%S')
print(tm)
def listener(event: ScheduleRemoved):
scheduler.stop()
class PatchedScheduler(Scheduler):
def subscribe(
self,
callback,
event_types = None,
*,
one_shot: bool = False,
):
self._ensure_services_ready()
return self._portal.call(
partial(
self._async_scheduler.subscribe,
callback,
event_types,
is_async=False,
one_shot=one_shot,
)
)
with PatchedScheduler() as scheduler:
d = datetime.now() + timedelta(seconds=20)
end_time = d.astimezone(ZoneInfo('Europe/Paris'))
scheduler.add_schedule(fn,
CronTrigger(second='0, 10, 20, 30, 40, 50', end_time=end_time),
misfire_grace_time=None,
max_running_jobs=1)
scheduler.subscribe(listener, {ScheduleRemoved})
scheduler.run_until_stopped() |
Beta Was this translation helpful? Give feedback.
-
|
This is working like a charm! Thank you. Just one other question: For asynchronous version, how can I pass the |
Beta Was this translation helpful? Give feedback.
-
from functools import partial
...
async def listener(scheduler, event: ScheduleRemoved):
await scheduler.stop()
...
scheduler.subscribe(partial(listener, scheduler), {ScheduleRemoved}) |
Beta Was this translation helpful? Give feedback.
-
|
The async scheduler does not have the aforementioned bug btw. |
Beta Was this translation helpful? Give feedback.
-
|
I am extremely grateful for your assistance. |
Beta Was this translation helpful? Give feedback.
Hmm...this looks like a bug in the synchronous scheduler interface. It worked for me because I had already fixed this locally. This will be rectified in the next release.
For now, you can patch the method locally: