ask/django-celery — pull request #116 by mlavin (2012-03-07 01:56:47+00:00)
Title: ALWAYS_EAGER tasks with Celery 2.5

This is a continuation of a discussion from celery-users: http://groups.google.com/group/celery-users/browse_thread/thread/855aa1ef7f3eee5d

These test cases demonstrate a problem related to running tasks with `CELERY_ALWAYS_EAGER` with Celery 2.5 and Django-Celery. This is most commonly used when running the test suite. I've created a simple model and a task which uses that model. As you'll see without the proposed change to the loader `test_apply_task` fails with Celery 2.5 but passes with 2.4 or with the proposed change. To see this failure you must be using a DB backend with supports transactions. I've changed the test settings to use Postgres just to demonstrate the problem. I'm happy to revert or reorganize any of these tests. Let the discussion begin!