Deprecate DjangoLoader

Currently, we have two ways of running Django with Celery:

• DjangoLoader (via djcelery.setup_loader()) as written in README.
• DjangoFixup which is applied automatically by Celery 3.1+, when using Django and not DjangoLoader.

AFAICT, the only benefit of using DjangoLoader over DjangoFixup is being able to use CELERY_RESULT_BACKEND = 'database' instead of CELERY_RESULT_BACKEND = 'djcelery.backends.database:DatabaseBackend'.

So, maybe it would make sense to deprecate DjangoLoader and have the one way to integrate Django and Celery?

[vytisb]

@ask For me, one big advantage of celerycam over Flower is that I don’t need to run a separate HTTP server and manage another set of auth credentials. I don’t have a lot of tasks so the database usage is low; and I don’t require a real-time API.

celerycam works now. So why not make an extension out of it and let people choose what works better for them? Or is it too much work to port it to Celery 4.0?

Of course, embedding Flower into admin would also solve my problems 😃

[vytisb]

@auvipy Can you explain what do you have in mind? And how it will be different from Flower or celerycam?