PageRenderTime 25ms CodeModel.GetById 28ms RepoModel.GetById 0ms app.codeStats 0ms

/venv/Lib/site-packages/APScheduler-3.3.0.dist-info/DESCRIPTION.rst

https://bitbucket.org/lina_wang_veeva/vone
ReStructuredText | 75 lines | 51 code | 24 blank | 0 comment | 0 complexity | bd2357112a836b61c98fcf8959740bde MD5 | raw file
  1. .. image:: https://travis-ci.org/agronholm/apscheduler.svg?branch=master
  2. :target: https://travis-ci.org/agronholm/apscheduler
  3. :alt: Build Status
  4. .. image:: https://coveralls.io/repos/github/agronholm/apscheduler/badge.svg?branch=master
  5. :target: https://coveralls.io/github/agronholm/apscheduler?branch=master
  6. :alt: Code Coverage
  7. Advanced Python Scheduler (APScheduler) is a Python library that lets you schedule your Python code to be executed
  8. later, either just once or periodically. You can add new jobs or remove old ones on the fly as you please. If you store
  9. your jobs in a database, they will also survive scheduler restarts and maintain their state. When the scheduler is
  10. restarted, it will then run all the jobs it should have run while it was offline [#f1]_.
  11. Among other things, APScheduler can be used as a cross-platform, application specific replacement to platform specific
  12. schedulers, such as the cron daemon or the Windows task scheduler. Please note, however, that APScheduler is **not** a
  13. daemon or service itself, nor does it come with any command line tools. It is primarily meant to be run inside existing
  14. applications. That said, APScheduler does provide some building blocks for you to build a scheduler service or to run a
  15. dedicated scheduler process.
  16. APScheduler has three built-in scheduling systems you can use:
  17. * Cron-style scheduling (with optional start/end times)
  18. * Interval-based execution (runs jobs on even intervals, with optional start/end times)
  19. * One-off delayed execution (runs jobs once, on a set date/time)
  20. You can mix and match scheduling systems and the backends where the jobs are stored any way you like.
  21. Supported backends for storing jobs include:
  22. * Memory
  23. * `SQLAlchemy <http://www.sqlalchemy.org/>`_ (any RDBMS supported by SQLAlchemy works)
  24. * `MongoDB <http://www.mongodb.org/>`_
  25. * `Redis <http://redis.io/>`_
  26. * `RethinkDB <https://www.rethinkdb.com/>`_
  27. * `ZooKeeper <https://zookeeper.apache.org/>`_
  28. APScheduler also integrates with several common Python frameworks, like:
  29. * `asyncio <http://docs.python.org/3.4/library/asyncio.html>`_ (:pep:`3156`)
  30. * `gevent <http://www.gevent.org/>`_
  31. * `Tornado <http://www.tornadoweb.org/>`_
  32. * `Twisted <http://twistedmatrix.com/>`_
  33. * `Qt <http://qt-project.org/>`_ (using either `PyQt <http://www.riverbankcomputing.com/software/pyqt/intro>`_
  34. or `PySide <http://qt-project.org/wiki/PySide>`_)
  35. .. [#f1] The cutoff period for this is also configurable.
  36. Documentation
  37. -------------
  38. Documentation can be found `here <http://readthedocs.org/docs/apscheduler/en/latest/>`_.
  39. Source
  40. ------
  41. The source can be browsed at `Github <https://github.com/agronholm/apscheduler>`_.
  42. Reporting bugs
  43. --------------
  44. A `bug tracker <https://github.com/agronholm/apscheduler/issues>`_ is provided by Github.
  45. Getting help
  46. ------------
  47. If you have problems or other questions, you can either:
  48. * Ask on the ``#apscheduler`` channel on `Freenode IRC <http://freenode.net/irc_servers.shtml>`_
  49. * Ask on the `APScheduler Google group <http://groups.google.com/group/apscheduler>`_, or
  50. * Ask on `StackOverflow <http://stackoverflow.com/questions/tagged/apscheduler>`_ and tag your question with the
  51. ``apscheduler`` tag