Changelog 6.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176
  1. ==============
  2. Change history
  3. ==============
  4. 0.2.0-pre2 [2009-05-20 01:56 P.M CET] askh@opera.com
  5. ----------------------------------------------------
  6. * Now handles unpickleable exceptions (like the dynimically generated
  7. subclasses of ``django.core.exception.MultipleObjectsReturned``).
  8. 0.2.0-pre1 [2009-05-20 12:33 P.M CET] askh@opera.com
  9. ----------------------------------------------------
  10. * It's getting quite stable, with a lot of new features, so bump
  11. version to 0.2. This is a pre-release.
  12. * ``celery.task.mark_as_read()`` and ``celery.task.mark_as_failure()`` has
  13. been removed. Use ``celery.backends.default_backend.mark_as_read()``,
  14. and ``celery.backends.default_backend.mark_as_failure()`` instead.
  15. 0.1.15 [2009-05-19 04:13 P.M CET] askh@opera.com
  16. ------------------------------------------------
  17. * The celery daemon was leaking AMQP connections, this should be fixed,
  18. if you have any problems with too many files open (like ``emfile``
  19. errors in ``rabbit.log``, please contact us!
  20. 0.1.14 [2009-05-19 01:08 P.M CET] askh@opera.com
  21. ------------------------------------------------
  22. * Fixed a syntax error in the ``TaskSet`` class. (No such variable
  23. ``TimeOutError``).
  24. 0.1.13 [2009-05-19 12:36 P.M CET] askh@opera.com
  25. ------------------------------------------------
  26. * Forgot to add ``yadayada`` to install requirements.
  27. * Now deletes all expired task results, not just those marked as done.
  28. * Able to load the Tokyo Tyrant backend class without django
  29. configuration, can specify tyrant settings directly in the class
  30. constructor.
  31. * Improved API documentation
  32. * Now using the Sphinx documentation system, you can build
  33. the html documentation by doing ::
  34. $ cd docs
  35. $ make html
  36. and the result will be in ``docs/.build/html``.
  37. 0.1.12 [2009-05-18 04:38 P.M CET] askh@opera.com
  38. ------------------------------------------------
  39. * ``delay_task()`` etc. now returns ``celery.task.AsyncResult`` object,
  40. which lets you check the result and any failure that might have
  41. happened. It kind of works like the ``multiprocessing.AsyncResult``
  42. class returned by ``multiprocessing.Pool.map_async``.
  43. * Added dmap() and dmap_async(). This works like the
  44. ``multiprocessing.Pool`` versions except they are tasks
  45. distributed to the celery server. Example:
  46. >>> from celery.task import dmap
  47. >>> import operator
  48. >>> dmap(operator.add, [[2, 2], [4, 4], [8, 8]])
  49. >>> [4, 8, 16]
  50. >>> from celery.task import dmap_async
  51. >>> import operator
  52. >>> result = dmap_async(operator.add, [[2, 2], [4, 4], [8, 8]])
  53. >>> result.ready()
  54. False
  55. >>> time.sleep(1)
  56. >>> result.ready()
  57. True
  58. >>> result.result
  59. [4, 8, 16]
  60. * Refactored the task metadata cache and database backends, and added a new backend for Tokyo Tyrant. You can set the backend in your django settings file. e.g
  61. CELERY_BACKEND = "database"; # Uses the database
  62. CELERY_BACKEND = "cache"; # Uses the django cache framework
  63. CELERY_BACKEND = "tyrant"; # Uses Tokyo Tyrant
  64. TT_HOST = "localhost"; # Hostname for the Tokyo Tyrant server.
  65. TT_PORT = 6657; # Port of the Tokyo Tyrant server.
  66. 0.1.11 [2009-05-12 02:08 P.M CET] askh@opera.com
  67. -------------------------------------------------
  68. * The logging system was leaking file descriptors, resulting in
  69. servers stopping with the EMFILES (too many open files) error. (fixed)
  70. 0.1.10 [2009-05-11 12:46 P.M CET] askh@opera.com
  71. -------------------------------------------------
  72. * Tasks now supports both positional arguments and keyword arguments.
  73. * Requires carrot 0.3.8.
  74. * The daemon now tries to reconnect if the connection is lost.
  75. 0.1.8 [2009-05-07 12:27 P.M CET] askh@opera.com
  76. ------------------------------------------------
  77. * Better test coverage
  78. * More documentation
  79. * celeryd doesn't emit ``Queue is empty`` message if
  80. ``settings.CELERYD_EMPTY_MSG_EMIT_EVERY`` is 0.
  81. 0.1.7 [2009-04-30 1:50 P.M CET] askh@opera.com
  82. -----------------------------------------------
  83. * Added some unittests
  84. * Can now use the database for task metadata (like if the task has
  85. been executed or not). Set ``settings.CELERY_TASK_META``
  86. * Can now run ``python setup.py test`` to run the unittests from
  87. within the ``testproj`` project.
  88. * Can set the AMQP exchange/routing key/queue using
  89. ``settings.CELERY_AMQP_EXCHANGE``, ``settings.CELERY_AMQP_ROUTING_KEY``,
  90. and ``settings.CELERY_AMQP_CONSUMER_QUEUE``.
  91. 0.1.6 [2009-04-28 2:13 P.M CET] askh@opera.com
  92. -----------------------------------------------
  93. * Introducing ``TaskSet``. A set of subtasks is executed and you can
  94. find out how many, or if all them, are done (excellent for progress bars and such)
  95. * Now catches all exceptions when running ``Task.__call__``, so the
  96. daemon doesn't die. This does't happen for pure functions yet, only
  97. ``Task`` classes.
  98. * ``autodiscover()`` now works with zipped eggs.
  99. * celeryd: Now adds curernt working directory to ``sys.path`` for
  100. convenience.
  101. * The ``run_every`` attribute of ``PeriodicTask`` classes can now be a
  102. ``datetime.timedelta()`` object.
  103. * celeryd: You can now set the ``DJANGO_PROJECT_DIR`` variable
  104. for ``celeryd`` and it will add that to ``sys.path`` for easy launching.
  105. * Can now check if a task has been executed or not via HTTP.
  106. You can do this by including the celery ``urls.py`` into your project,
  107. >>> url(r'^celery/$', include("celery.urls"))
  108. then visiting the following url,::
  109. http://mysite/celery/$task_id/done/
  110. this will return a JSON dictionary like e.g:
  111. >>> {"task": {"id": $task_id, "executed": true}}
  112. * ``delay_task`` now returns string id, not ``uuid.UUID`` instance.
  113. * Now has ``PeriodicTasks``, to have ``cron`` like functionality.
  114. * Project changed name from ``crunchy`` to ``celery``. The details of
  115. the name change request is in ``docs/name_change_request.txt``.
  116. 0.1.0 [2009-04-24 11:28 A.M CET] askh@opera.com
  117. ------------------------------------------------
  118. * Initial release