It is what it says it is – a warning that
settings.DEBUG should not be set for production deployments. If you’re just using it for development, then it is not something to be concerned about. In general, this ought to apply whether you use django-celery or not.
I have not looked up the details, but as mentioned in this answer:
DEBUGis enabled Django appends every executed SQL statement to
django.db.connection.queries, this will grow unbounded in a long running process environment.
The officially recommended way to start celeryd for django-celery is:
python manage.py celeryd --setting=settings
Today, I forgot this and directly start celeryd by
python -m celery.bin.celeryd --config=settings
and viola, no warnings! And it works just fine! The Celery group really need to work on their docs. Although it seems comprehensive, some key pieces are missing to cover all the grounds imho.
- If I send a python 'Signal' object from a function, what should the "sender" argument be?
- Where are the files downloaded using pip stored in virtualenv?
- Error Using CheckConstraint in Model.Meta along with Django GenericForeignKey – Joined field references are not permitted in this query
Actually… Django stopped leaking memory in Django 1.8 https://github.com/django/django/commit/cfcca7ccce3dc527d16757ff6dc978e50c4a2e61
A fix for celery such that it won’t complain anymore is underway.
- How do I use perform_create to set a field automatically in Django Rest Framework?
- Docker crontab: not found
- Django, Postgres – column cannot be cast automatically to type integer
- How to restrict Django Rest Framework browsable API interface to admin users
As of Django 1.8, Django no longer leaks memory when
- Background processing in Django without Celery
- Group models in django admin
- Getting scrapy project settings when script is outside of root directory
- Django admin – select reverse foreign key relationships (not create, I want to add available)