Changelog for python-apscheduler-2.0.2-3.1.x86_64.rpm :

* Tue Aug 16 2011 cfarrellAATTnovell.com2.0.2-----
* Removed the unique constraint from the \"name\" column in the SQLAlchemy job store
* Fixed output from Scheduler.print_jobs() which did not previously output a line ending at the end 2.0.1-----
* Fixed cron style jobs getting wrong default values 2.0.0-----
* Added configurable job stores with several persistent back-ends (shelve, SQLAlchemy and MongoDB)
* Added the possibility to listen for job events (execution, error, misfire, finish) on a scheduler
* Added an optional start time for cron-style jobs
* Added optional job execution coalescing for situations where several executions of the job are due
* Added an option to limit the maximum number of concurrenctly executing instances of the job
* Allowed configuration of misfire grace times on a per-job basis
* Allowed jobs to be explicitly named
* 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 its own
* Maximum run count can be configured for all jobs, not just those using interval-based scheduling
* 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)
* Changed defaults for cron-style jobs to be more intuitive -- it will now default to all minimum values for fields lower than the least significant explicitly defined field
* Thu Feb 17 2011 cfarrellAATTnovell.com- First attempt at building