Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


Django-Sprinklers imposes structure on jobs that perform asynchronous processing of Django models.

Specify a queryset and a function to perform on each object in the queryset and Sprinklers will distribute your queryset into a group of asynchronous jobs, perform logging, and track the status of each job.

Using this wrapper you can avoid repeatedly writing fiddly bits of celery code and repetitive logging so you can focus on your business logic.

For example

At a high level celery cron jobs often take the form of "run this queryset, and take an action on each object." For example:

  • Find all customers that should be billed for our recurring service, and bill them.
  • Find all users who should receive a welcome email, and send them each a message.
  • For each product listing, update the details from an external service.
  • etc. etc.

Typically code for these cron tasks would look something like:

from celery import task

def refresh_objects():"Starting refresh objects...")
    qs = Item.objects.all()
    for obj in qs:
        if obj.needs_update():
            # Remember to pass 'id' and not the object itself!
            # Remember to call .delay on the task!
            get_updated_item_from_slow_external_service.delay("I would love to say 'finished' here, but I spawned a bunch of async tasks and can't actually do that...")

def get_updated_field_from_slow_external_service(id):
        item = Item.objects.get(pk=id)
    except Item.DoesNotExist:"grrr...")"Starting update of item %s..." % id)
    item.field = ExternalServiceWrapper().get(id)['field']"Successful update of item %s." % id)

This is fine, but as logic gets more complex and as you add more jobs that follow a similar pattern, you'll find that you handle logging slightly differently from job to job, that you want to run code after all the subtasks have completed, and in general things are looking a bit messy.

Use Sprinklers to impose structure and make these jobs testable.


from sprinklers.base import SprinklerBase, registry, SubtaskValidationException

class ItemUpdateSprinkler(SprinklerBase):

    def get_queryset():
        return Item.objects.all()

    def validate(obj)
        if not obj.needs_update():
            raise SubtaskValidationException()

    def subtask(obj):
        obj.field = ExternalServiceWrapper().get(['field']
        return  # gets aggregated into a results argument

    def finished(results):"Updated %s items." % len(results))

# This is the entry point to the job. You can use it in your crontab configuration as normal:

#     'item.tasks.start_item_sprinkler': {
#         'task': 'item.tasks.start_item_sprinkler',
#         'schedule': crontab(hour=24, minute=0),
#     },

def start_item_sprinkler():

You can also pass **kwargs into the Sprinkler's start() function, which will be accessible downstream to all Sprinkler methods. See and in /tests for how this works.


The Sprinkler tests are a bit trickier to run that just ' test' because every attempt has been made to mimic an async production celery environment.

In order to run the tests you will need:

  1. Change CELERY_ALWAYS_EAGER = False in
  2. A local postgres server set up in line with the DB config in test.settings
  3. A running redis server with default localhost config (redis://localhost:6379/0)
  4. A running celery daemon/worker.
  5. Then run 'python test'

I find it easiest to run 2 & 3 via:

screen -d -S 'redis' -m redis-server
screen -d -S 'celery' -m python celeryd

This will run each in the background, and you can 'screen -r redis' or 'screen -r celery' to view them (Ctrl-a-d to detach).

If you are working on this project directly, remember to restart celery after code changes to django-sprinklers. Celery does not live reload!


  • Q: Will this work on any iterable? Does it have to be a Django queryset?
  • A: It has to be a queryset (or a valuesqueryset). Sprinklers relies on some introspection to determine which model class to use for individual object retrieval.


A simple framework for bulletproof distributed tasks with Django and Celery.






No releases published


No packages published