As explored previously, the RPC result backend works by having a results queue per client, unfortunately celery-batches was attempting to store the results …read more →
celery-batches is a small library that allows you process multiple calls to a Celery …read more →
This started as notes explaining the internals of how Celery’s AMQP backends operate. This isn’t meant to be a comparison or prove one is better or that one is broken. There just seemed to be a lack of documentation about the design and limitations of each backend …
The Celery send_task method allows you to invoke a task by name without importing it.  There is an undocumented  caveat to using send_task: it doesn’t have access to the configuration of the task (from when the task was created using the @task decorator).
Much of this configuration …read more →
I use Twisted and Celery daily at work, both are useful frameworks, both have a lot of great information out there, but a particular use (that I haven’t seen discussed much online, hence this post) is calling Celery tasks from Twisted (and subsequently using the result).
The difference …