Migrating from APScheduler v1.x to 2.0¶

There have been some API changes since the 1.x series. This document explains the changes made to v2.0 that are incompatible with the v1.x API.

API changes¶

The behavior of cron scheduling with regards to default values for omitted fields has been made more intuitive – omitted fields lower than the least significant explicitly defined field will default to their minimum values except for the week number and weekday fields
SchedulerShutdownError has been removed – jobs are now added tentatively and scheduled for real when/if the scheduler is restarted
Scheduler.is_job_active() has been removed – use job in scheduler.get_jobs() instead
dump_jobs() is now print_jobs() and prints directly to the given file or sys.stdout if none is given
The repeat parameter was removed from add_interval_job() and interval_schedule() in favor of the universal max_runs option
unschedule_func() now raises a KeyError if the given function is not scheduled
The semantics of shutdown() have changed – the method no longer accepts a numeric argument, but two booleans