diff options
| author | agronholm <devnull@localhost> | 2011-02-08 04:54:39 +0200 |
|---|---|---|
| committer | agronholm <devnull@localhost> | 2011-02-08 04:54:39 +0200 |
| commit | a8b7b77b73b782a04d8c8b828ec3a1a4d3f32c5a (patch) | |
| tree | cbe4a228271c72322571d12a3563f38363567d35 | |
| parent | be9c0fa690266ab61ff127f1c9668e6d50404a5f (diff) | |
| download | apscheduler-a8b7b77b73b782a04d8c8b828ec3a1a4d3f32c5a.tar.gz | |
Added a note about the v1.x design flaw fix
| -rw-r--r-- | CHANGES.rst | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/CHANGES.rst b/CHANGES.rst index bf8d8e6..4d9eb7e 100644 --- a/CHANGES.rst +++ b/CHANGES.rst @@ -6,7 +6,7 @@ Version history * Added configurable job stores -* Added optional job persistency +* Added optional job persistency (via shelve, SQLAlchemy or MongoDB) * Added the possibility to listen for job events (execution, error, misfire, finish) on a scheduler @@ -17,7 +17,7 @@ Version history * Allowed jobs to be explicitly named -* All triggers now accept dates in string form (YYYY-m-d HH:MM:SS) +* All triggers now accept dates in string form (YYYY-mm-dd HH:MM:SS) * Jobs are now run in a thread pool; you can either supply your own PEP 3148 compliant thread pool or let APScheduler create a new one @@ -28,6 +28,10 @@ Version history * A maximum concurrency value can be configured for jobs, so only X instances will be allowed to run at once (will be considered a misfire otherwise) +* Fixed a v1.x design flaw that caused jobs to be executed twice when the + scheduler thread was woken up while still within the allowable range of their + previous execution time (issues #5, #7) + Some API changes were necessary -- see the migration section of the documentation to find out what you need to change when migrating your application from APScheduler v1.x to v2.0. |