Changelog 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386
  1. .. _changelog:
  2. ================
  3. Change history
  4. ================
  5. .. contents::
  6. :local:
  7. If you're looking for versions prior to 3.x you should see :ref:`history`.
  8. .. _version-3.0.6:
  9. 3.0.6
  10. =====
  11. :release-date: 2012-09-XX XX:XX X.M BST
  12. - Now depends on kombu 2.4.0
  13. - Now depends on billiard 2.7.3.12
  14. - Redis: Celery now tries to restore messages whenever there are no messages
  15. in the queue.
  16. - Crontab schedules now properly respects :setting:`CELERY_TIMEZONE` setting.
  17. It's important to note that crontab schedules uses UTC time by default
  18. unless this setting is set.
  19. Issue #904 and django-celery #150.
  20. - ``billiard.enable_forking`` is now only set by the processes pool.
  21. - The transport is now properly shown by :program:`celery report`
  22. (Issue #913).
  23. - The `--app` argument now works if the last part is a module name
  24. (Issue #921).
  25. - Fixed problem with unpickleable exceptions (billiard #12).
  26. - Adds ``task_name`` attribute to ``EagerResult`` which is always
  27. :const:`None` (Issue #907).
  28. - Old Task class in :mod:`celery.task` no longer accepts magic kwargs by
  29. default (Issue #918).
  30. A regression long ago disabled magic kwargs for these, and since
  31. no one has complained about it we don't have any incentive to fix it now.
  32. - The ``inspect reserved`` control command did not work properly.
  33. - Should now play better with static analyzation tools by explicitly
  34. specifying dynamically created attributes in the :mod:`celery` and
  35. :mod:`celery.task` modules.
  36. - Terminating a task now results in
  37. :exc:`~celery.exceptions.RevokedTaskError` instead of a ``WorkerLostError``.
  38. - ``AsyncResult.revoke`` now accepts ``terminate`` and ``signal`` arguments.
  39. - The ``task-revoked`` event now includes new fields: ``terminated``,
  40. ``signum``, and ``expired``.
  41. - The argument to :class:`~celery.exceptions.TaskRevokedError` is now one
  42. of the reasons ``revoked``, ``expired`` or ``terminated``.
  43. - Old Task class does no longer use classmethods for push_request and
  44. pop_request (Issue #912).
  45. - ``GroupResult`` now supports the ``children`` attribute (Issue #916).
  46. - ``AsyncResult.collect`` now respects the ``intermediate`` argument
  47. (Issue #917).
  48. - Fixes example task in documentation (Issue #902).
  49. - Eventlet fixed so that the environment is patched as soon as possible.
  50. - eventlet: Now warns if celery related modules that depends on threads
  51. are imported before eventlet is patched.
  52. - Improved event and camera examples in the monitoring guide.
  53. - Disables celery command setuptools entrypoints if the command can't be
  54. loaded.
  55. - Fixed broken ``dump_request`` example in the tasks guide.
  56. .. _version-3.0.5:
  57. 3.0.5
  58. =====
  59. :release-date: 2012-08-01 04:00 P.M BST
  60. - Now depends on kombu 2.3.1 + billiard 2.7.3.11
  61. - Fixed a bug with the -B option (``cannot pickle thread.lock objects``)
  62. (Issue #894 + Issue #892, + django-celery #154).
  63. - The :control:`restart_pool` control command now requires the
  64. :setting:`CELERYD_POOL_RESTARTS` setting to be enabled
  65. This change was necessary as the multiprocessing event that the restart
  66. command depends on is responsible for creating many semaphores/file
  67. descriptors, resulting in problems in some environments.
  68. - ``chain.apply`` now passes args to the first task (Issue #889).
  69. - Documented previously secret options to the Django-Celery monitor
  70. in the monitoring userguide (Issue #396).
  71. - Old changelog are now organized in separate documents for each series,
  72. see :ref:`history`.
  73. .. _version-3.0.4:
  74. 3.0.4
  75. =====
  76. :release-date: 2012-07-26 07:00 P.M BST
  77. - Now depends on Kombu 2.3
  78. - New experimental standalone Celery monitor: Flower
  79. See :ref:`monitoring-flower` to read more about it!
  80. Contributed by Mher Movsisyan.
  81. - Now supports AMQP heartbeats if using the new ``pyamqp://`` transport.
  82. - The py-amqp transport requires the :mod:`amqp` library to be installed::
  83. $ pip install amqp
  84. - Then you need to set the transport URL prefix to ``pyamqp://``.
  85. - The default heartbeat value is 10 seconds, but this can be changed using
  86. the :setting:`BROKER_HEARTBEAT` setting::
  87. BROKER_HEARTBEAT = 5.0
  88. - If the broker heartbeat is set to 10 seconds, the heartbeats will be
  89. monitored every 5 seconds (double the hertbeat rate).
  90. See the `Kombu 2.3 changelog`_ for more information.
  91. .. _`Kombu 2.3 changelog`:
  92. http://kombu.readthedocs.org/en/latest/changelog.html#version-2-3-0
  93. - Now supports RabbitMQ Consumer Cancel Notifications, using the ``pyamqp://``
  94. transport.
  95. This is essential when running RabbitMQ in a cluster.
  96. See the `Kombu 2.3 changelog`_ for more information.
  97. - Delivery info is no longer passed directly through.
  98. It was discovered that the SQS transport adds objects that can't
  99. be pickled to the delivery info mapping, so we had to go back
  100. to using the whitelist again.
  101. Fixing this bug also means that the SQS transport is now working again.
  102. - The semaphore was not properly released when a task was revoked (Issue #877).
  103. This could lead to tasks being swallowed and not released until a worker
  104. restart.
  105. Thanks to Hynek Schlawack for debugging the issue.
  106. - Retrying a task now also forwards any linked tasks.
  107. This means that if a task is part of a chain (or linked in some other
  108. way) and that even if the task is retried, then the next task in the chain
  109. will be executed when the retry succeeds.
  110. - Chords: Now supports setting the interval and other keyword arguments
  111. to the chord unlock task.
  112. - The interval can now be set as part of the chord subtasks kwargs::
  113. chord(header)(body, interval=10.0)
  114. - In addition the chord unlock task now honors the Task.default_retry_delay
  115. option, used when none is specified, which also means that the default
  116. interval can also be changed using annotations:
  117. .. code-block:: python
  118. CELERY_ANNOTATIONS = {
  119. 'celery.chord_unlock': {
  120. 'default_retry_delay': 10.0,
  121. }
  122. }
  123. - New :meth:`@Celery.add_defaults` method can add new default configuration
  124. dicts to the applications configuration.
  125. For example::
  126. config = {'FOO': 10}
  127. celery.add_defaults(config)
  128. is the same as ``celery.conf.update(config)`` except that data will not be
  129. copied, and that it will not be pickled when the worker spawns child
  130. processes.
  131. In addition the method accepts a callable::
  132. def initialize_config():
  133. # insert heavy stuff that can't be done at import time here.
  134. celery.add_defaults(initialize_config)
  135. which means the same as the above except that it will not happen
  136. until the celery configuration is actually used.
  137. As an example, Celery can lazily use the configuration of a Flask app::
  138. flask_app = Flask()
  139. celery = Celery()
  140. celery.add_defaults(lambda: flask_app.config)
  141. - Revoked tasks were not marked as revoked in the result backend (Issue #871).
  142. Fix contributed by Hynek Schlawack.
  143. - Eventloop now properly handles the case when the epoll poller object
  144. has been closed (Issue #882).
  145. - Fixed syntax error in ``funtests/test_leak.py``
  146. Fix contributed by Catalin Iacob.
  147. - group/chunks: Now accepts empty task list (Issue #873).
  148. - New method names:
  149. - ``Celery.default_connection()`` ➠ :meth:`~@Celery.connection_or_acquire`.
  150. - ``Celery.default_producer()`` ➠ :meth:`~@Celery.producer_or_acquire`.
  151. The old names still work for backward compatibility.
  152. .. _version-3.0.3:
  153. 3.0.3
  154. =====
  155. :release-date: 2012-07-20 09:17 P.M BST
  156. :by: Ask Solem
  157. - amqplib passes the channel object as part of the delivery_info
  158. and it's not pickleable, so we now remove it.
  159. .. _version-3.0.2:
  160. 3.0.2
  161. =====
  162. :release-date: 2012-07-20 04:00 P.M BST
  163. :by: Ask Solem
  164. - A bug caused the following task options to not take defaults from the
  165. configuration (Issue #867 + Issue #858)
  166. The following settings were affected:
  167. - :setting:`CELERY_IGNORE_RESULT`
  168. - :setting:`CELERYD_SEND_TASK_ERROR_EMAILS`
  169. - :setting:`CELERY_TRACK_STARTED`
  170. - :setting:`CElERY_STORE_ERRORS_EVEN_IF_IGNORED`
  171. Fix contributed by John Watson.
  172. - Task Request: ``delivery_info`` is now passed through as-is (Issue #807).
  173. - The eta argument now supports datetime's with a timezone set (Issue #855).
  174. - The worker's banner displayed the autoscale settings in the wrong order
  175. (Issue #859).
  176. - Extension commands are now loaded after concurrency is set up
  177. so that they don't interfere with e.g. eventlet patching.
  178. - Fixed bug in the threaded pool (Issue #863)
  179. - The task failure handler mixed up the fields in :func:`sys.exc_info`.
  180. Fix contributed by Rinat Shigapov.
  181. - Fixed typos and wording in the docs.
  182. Fix contributed by Paul McMillan
  183. - New setting: :setting:`CELERY_WORKER_DIRECT`
  184. If enabled each worker will consume from their own dedicated queue
  185. which can be used to route tasks to specific workers.
  186. - Fixed several edge case bugs in the add consumer remote control command.
  187. - :mod:`~celery.contrib.migrate`: Can now filter and move tasks to specific
  188. workers if :setting:`CELERY_WORKER_DIRECT` is enabled.
  189. Among other improvements, the following functions have been added:
  190. * ``move_direct(filterfun, **opts)``
  191. * ``move_direct_by_id(task_id, worker_hostname, **opts)``
  192. * ``move_direct_by_idmap({task_id: worker_hostname, ...}, **opts)``
  193. * ``move_direct_by_taskmap({task_name: worker_hostname, ...}, **opts)``
  194. - :meth:`~celery.Celery.default_connection` now accepts a pool argument that
  195. if set to false causes a new connection to be created instead of acquiring
  196. one from the pool.
  197. - New signal: :signal:`celeryd_after_setup`.
  198. - Default loader now keeps lowercase attributes from the configuration module.
  199. .. _version-3.0.1:
  200. 3.0.1
  201. =====
  202. :release-date: 2012-07-10 06:00 P.M BST
  203. :by: Ask Solem
  204. - Now depends on kombu 2.2.5
  205. - inspect now supports limit argument::
  206. myapp.control.inspect(limit=1).ping()
  207. - Beat: now works with timezone aware datetime's.
  208. - Task classes inheriting ``from celery import Task``
  209. mistakingly enabled ``accept_magic_kwargs``.
  210. - Fixed bug in ``inspect scheduled`` (Issue #829).
  211. - Beat: Now resets the schedule to upgrade to UTC.
  212. - The :program:`celery worker` command now works with eventlet/gevent.
  213. Previously it would not patch the environment early enough.
  214. - The :program:`celery` command now supports extension commands
  215. using setuptools entry-points.
  216. Libraries can add additional commands to the :program:`celery`
  217. command by adding an entry-point like::
  218. setup(
  219. entry_points=[
  220. 'celery.commands': [
  221. 'foo = my.module:Command',
  222. ],
  223. ],
  224. ...)
  225. The command must then support the interface of
  226. :class:`celery.bin.base.Command`.
  227. - contrib.migrate: New utilities to move tasks from one queue to another.
  228. - :func:`~celery.contrib.migrate.move_tasks`
  229. - :func:`~celery.contrib.migrate.move_task_by_id`
  230. - The task-sent event now contains ``exchange`` and ``routing_key``
  231. fields.
  232. - Fixes bug with installing on Python 3.
  233. Fix contributed by Jed Smith.
  234. .. _version-3.0.0:
  235. 3.0.0 (Chiastic Slide)
  236. ======================
  237. :release-date: 2012-07-07 01:30 P.M BST
  238. :by: Ask Solem
  239. See :ref:`whatsnew-3.0`.