Clarify project status and django support

[craigds]

This is apparently the 'old' project for integrating django with celery, but it's not clear what the new approach should be.

The celery docs still mention this project as the recommended way to use the django database as a backend (see http://docs.celeryproject.org/en/latest/django/first-steps-with-django.html#using-the-django-orm-cache-as-a-result-backend )

However this project doesn't appear to be compatible with django 1.8 (e.g. it uses South migrations, which isn't compatible with django 1.8)

What's the recommended upgrade path for users upgrading to django 1.8?

[adriaant]

#356

[jensenbox]

I probably would have been oblivious to the status of this project had our development deployment not failed.

It turns out we were auto upgrading the pip packages and all of a sudden a day or so ago (Oct 9, 2015) it started to complain in the migrate

django.db.utils.ProgrammingError: relation "djcelery_crontabschedule" already exists

I went an looked on my dev box and we are using 3.1.16 of 'django-celery' - I upgraded to 3.1.17 and bang, it died in the migrate too.

We are on Django 1.8 and do not see any option to the things django-celery provides in the base celery package. I like the ability of using the admin interface to enable and disable certain jobs.

Can someone clarify what the exact status of this project is?

Thanks!

[natoinet]

Could you please clarify that, without prior notice, djcelery is not supported anymore?
Of course, with Flower, TaskState and WorkerState do not make much sense.
However, the bundle PeriodicTask, IntervalSchedule & CrontabSchedule is super practical for launching tasks easily in Django!

[trevoriancox]

This question is still valid. django-celery is still needed despite what the README says. From http://docs.celeryproject.org/en/latest/django/first-steps-with-django.html:

"If you want to store task results in the Django database then you still need to install the django-celery library for that (alternatively you can use the [unstable] SQLAlchemy result backend)."

In our case, we generally ignore results, but want to capture certain task results the simplest way possible.

[zborboa-g]

django-celery seems to still be needed to include the admin functionality as well.

[malefice]

@ask what is the official stance concerning this project's status? The django admin functionality is really good and convenient, and it would be a waste to just abandon this project.

[JanMalte]

Is this project still under active development?
If not, is there any successor?

The current version can not be used with Django 1.9's AppConfig in INSTALLED_APPS, as autodiscover is not working anymore.

[natoinet]

I am using it on Django 1.8, but have not upgraded yet to Django 1.9. I agree that the status should be clarified.

[psychok7]

I have tried the latest commit with Django 1.10 and it appears to be working..

Anyways this project is still needed in my opinion.

[auvipy]

Yes it is.try the master branch

[Romeus]

I use packages:
celery (3.1.23)
django-celery (3.2.0a1)
django (1.8.4)

Tasks are run, but there is no any statistics appear in 'task states' (/admin/djcelery/taskmeta/).
Is it possible to solve this problem ?

Also I tried to use django-celery 3.1.16 and 3.1.17, but without any results.

[auvipy]

@Romeus try 3.2.0