|
|
@@ -1632,7 +1632,7 @@ News
|
|
|
:class:`~celery.task.control.inspect`.
|
|
|
|
|
|
|
|
|
- Example using celeryctl to start consuming from queue "queue", in
|
|
|
+ Example using celeryctl to start consuming from queue "queue", in
|
|
|
exchange "exchange", of type "direct" using binding key "key"::
|
|
|
|
|
|
$ celeryctl inspect add_consumer queue exchange direct key
|
|
|
@@ -3555,7 +3555,7 @@ Fixes
|
|
|
by rounding to the nearest day/hour.
|
|
|
|
|
|
* Fixed a potential infinite loop in `BaseAsyncResult.__eq__`, although
|
|
|
- there is no evidence that it has ever been triggered.
|
|
|
+ there is no evidence that it has ever been triggered.
|
|
|
|
|
|
* celeryd: Now handles messages with encoding problems by acking them and
|
|
|
emitting an error message.
|
|
|
@@ -3618,7 +3618,7 @@ Fixes
|
|
|
|
|
|
* Execution: `.messaging.TaskPublisher.send_task` now
|
|
|
incorporates all the functionality apply_async previously did.
|
|
|
-
|
|
|
+
|
|
|
Like converting countdowns to eta, so :func:`celery.execute.apply_async` is
|
|
|
now simply a convenient front-end to
|
|
|
:meth:`celery.messaging.TaskPublisher.send_task`, using
|
|
|
@@ -3675,7 +3675,7 @@ Fixes
|
|
|
is revoked even though it's currently being hold because its eta is e.g.
|
|
|
a week into the future.
|
|
|
|
|
|
-* The `task_id` argument is now respected even if the task is executed
|
|
|
+* The `task_id` argument is now respected even if the task is executed
|
|
|
eagerly (either using apply, or :setting:`CELERY_ALWAYS_EAGER`).
|
|
|
|
|
|
* The internal queues are now cleared if the connection is reset.
|
|
|
@@ -3947,7 +3947,7 @@ News
|
|
|
... ([8, 8], {}, {"countdown": 3})])
|
|
|
>>> ts.run()
|
|
|
|
|
|
-* Got a 3x performance gain by setting the prefetch count to four times the
|
|
|
+* Got a 3x performance gain by setting the prefetch count to four times the
|
|
|
concurrency, (from an average task round-trip of 0.1s to 0.03s!).
|
|
|
|
|
|
A new setting has been added: :setting:`CELERYD_PREFETCH_MULTIPLIER`, which
|
|
|
@@ -4084,7 +4084,7 @@ Documentation
|
|
|
:release-date: 2009-11-20 03:40 P.M CEST
|
|
|
|
|
|
* QOS Prefetch count was not applied properly, as it was set for every message
|
|
|
- received (which apparently behaves like, "receive one more"), instead of only
|
|
|
+ received (which apparently behaves like, "receive one more"), instead of only
|
|
|
set when our wanted value changed.
|
|
|
|
|
|
.. _version-0.8.1:
|
|
|
@@ -4261,7 +4261,7 @@ Important changes
|
|
|
|
|
|
* Support for multiple AMQP exchanges and queues.
|
|
|
|
|
|
- This feature misses documentation and tests, so anyone interested
|
|
|
+ This feature misses documentation and tests, so anyone interested
|
|
|
is encouraged to improve this situation.
|
|
|
|
|
|
* celeryd now survives a restart of the AMQP server!
|
|
|
@@ -4384,7 +4384,7 @@ News
|
|
|
|
|
|
* Functions/methods with a timeout argument now works correctly.
|
|
|
|
|
|
-* New: `celery.strategy.even_time_distribution`:
|
|
|
+* New: `celery.strategy.even_time_distribution`:
|
|
|
With an iterator yielding task args, kwargs tuples, evenly distribute
|
|
|
the processing of its tasks throughout the time window available.
|
|
|
|
|
|
@@ -4547,7 +4547,7 @@ News
|
|
|
* Only use README as long_description if the file exists so easy_install
|
|
|
doesn't break.
|
|
|
|
|
|
-* `celery.view`: JSON responses now properly set its mime-type.
|
|
|
+* `celery.view`: JSON responses now properly set its mime-type.
|
|
|
|
|
|
* `apply_async` now has a `connection` keyword argument so you
|
|
|
can re-use the same AMQP connection if you want to execute
|
|
|
@@ -4733,7 +4733,7 @@ arguments, so be sure to flush your task queue before you upgrade.
|
|
|
version to 0.2. This is a pre-release.
|
|
|
|
|
|
* `celery.task.mark_as_read()` and `celery.task.mark_as_failure()` has
|
|
|
- been removed. Use `celery.backends.default_backend.mark_as_read()`,
|
|
|
+ been removed. Use `celery.backends.default_backend.mark_as_read()`,
|
|
|
and `celery.backends.default_backend.mark_as_failure()` instead.
|
|
|
|
|
|
.. _version-0.1.15:
|
|
|
@@ -4790,7 +4790,7 @@ arguments, so be sure to flush your task queue before you upgrade.
|
|
|
happened. It kind of works like the `multiprocessing.AsyncResult`
|
|
|
class returned by `multiprocessing.Pool.map_async`.
|
|
|
|
|
|
-* Added dmap() and dmap_async(). This works like the
|
|
|
+* Added dmap() and dmap_async(). This works like the
|
|
|
`multiprocessing.Pool` versions except they are tasks
|
|
|
distributed to the celery server. Example:
|
|
|
|
Gun.io Whitespace Robot