diff options
author | agronholm <devnull@localhost> | 2011-04-11 02:19:36 +0300 |
---|---|---|
committer | agronholm <devnull@localhost> | 2011-04-11 02:19:36 +0300 |
commit | 0915f85b7a2047c2469adc69ddcba2b14b104be8 (patch) | |
tree | a81a2d1acdbf043d22e9971f8a4200c18838ba2c /docs/migration.rst | |
parent | 379f7160e0fea545111e53fdf019e2ab7125bef2 (diff) | |
download | apscheduler-0915f85b7a2047c2469adc69ddcba2b14b104be8.tar.gz |
Readded Scheduler.unschedule_func(), which now raises a KeyError when no matching jobs are found; renamed max_concurrency to max_instances
Diffstat (limited to 'docs/migration.rst')
-rw-r--r-- | docs/migration.rst | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/docs/migration.rst b/docs/migration.rst index 5fce220..ccdb214 100644 --- a/docs/migration.rst +++ b/docs/migration.rst @@ -4,6 +4,7 @@ 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 ----------- @@ -14,9 +15,12 @@ API changes * 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 - :meth:`apscheduler.scheduler.Scheduler.add_interval_job` and - :meth:`apscheduler.scheduler.Scheduler.interval_schedule` in favor of the + :meth:`~apscheduler.scheduler.Scheduler.add_interval_job` and + :meth:`~apscheduler.scheduler.Scheduler.interval_schedule` in favor of the universal ``max_runs`` option +* :meth:`~apscheduler.scheduler.Scheduler.unschedule_func` now raises a + KeyError if the given function is not scheduled + Configuration changes --------------------- |