{"action":"created","issue":{"url":"https://api.github.com/repos/celery/django-celery/issues/474","repository_url":"https://api.github.com/repos/celery/django-celery","labels_url":"https://api.github.com/repos/celery/django-celery/issues/474/labels{/name}","comments_url":"https://api.github.com/repos/celery/django-celery/issues/474/comments","events_url":"https://api.github.com/repos/celery/django-celery/issues/474/events","html_url":"https://github.com/celery/django-celery/issues/474","id":179103664,"number":474,"title":"Deprecate DjangoLoader","user":{"login":"vytisb","id":5221624,"avatar_url":"https://avatars.githubusercontent.com/u/5221624?v=3","gravatar_id":"","url":"https://api.github.com/users/vytisb","html_url":"https://github.com/vytisb","followers_url":"https://api.github.com/users/vytisb/followers","following_url":"https://api.github.com/users/vytisb/following{/other_user}","gists_url":"https://api.github.com/users/vytisb/gists{/gist_id}","starred_url":"https://api.github.com/users/vytisb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vytisb/subscriptions","organizations_url":"https://api.github.com/users/vytisb/orgs","repos_url":"https://api.github.com/users/vytisb/repos","events_url":"https://api.github.com/users/vytisb/events{/privacy}","received_events_url":"https://api.github.com/users/vytisb/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-09-25T19:23:58Z","updated_at":"2016-10-17T20:52:07Z","closed_at":null,"body":"Currently, we have two ways of running Django with Celery:\r\n\r\n* `DjangoLoader` (via `djcelery.setup_loader()`) as written in [README](https://github.com/celery/django-celery/blob/master/README.rst#using-django-celery).\r\n* `DjangoFixup` which is applied automatically by Celery 3.1+, when using Django and not `DjangoLoader`.\r\n\r\nAFAICT, 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'`.\r\n\r\nSo, maybe it would make sense to deprecate `DjangoLoader` and have the one way [to integrate Django and Celery](http://docs.celeryproject.org/en/latest/django/first-steps-with-django.html)?"},"comment":{"url":"https://api.github.com/repos/celery/django-celery/issues/comments/254330338","html_url":"https://github.com/celery/django-celery/issues/474#issuecomment-254330338","issue_url":"https://api.github.com/repos/celery/django-celery/issues/474","id":254330338,"user":{"login":"km-pg","id":12038869,"avatar_url":"https://avatars.githubusercontent.com/u/12038869?v=3","gravatar_id":"","url":"https://api.github.com/users/km-pg","html_url":"https://github.com/km-pg","followers_url":"https://api.github.com/users/km-pg/followers","following_url":"https://api.github.com/users/km-pg/following{/other_user}","gists_url":"https://api.github.com/users/km-pg/gists{/gist_id}","starred_url":"https://api.github.com/users/km-pg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/km-pg/subscriptions","organizations_url":"https://api.github.com/users/km-pg/orgs","repos_url":"https://api.github.com/users/km-pg/repos","events_url":"https://api.github.com/users/km-pg/events{/privacy}","received_events_url":"https://api.github.com/users/km-pg/received_events","type":"User","site_admin":false},"created_at":"2016-10-17T20:52:07Z","updated_at":"2016-10-17T20:52:07Z","body":"Does this mean the \"Special note for mod_wsgi users\" in the README no longer applies if you are using Celery 3.1+?"}}
{"actor":{"display_login":"km-pg"}}