// the take
django-celery is the old glue package that wired Celery into Django before Celery 4.x absorbed Django support natively. It provides a Django ORM result backend, Django admin integration for tasks and periodic task management, and management commands that wrap Celery's CLI. If you're on Celery 5.x, you don't need this — Celery ships first-class Django support out of the box.
The Django admin integration for periodic tasks (via `djcelery.schedulers.DatabaseScheduler`) is still genuinely useful — letting non-engineers manage cron-style schedules through the admin without touching code or config files. The ORM-backed result backend is simple and works without Redis or RabbitMQ, which reduces infrastructure for small projects. The test runner contrib (`djcelery.contrib.test_runner`) sets ALWAYS_EAGER automatically, which saves boilerplate in test setup.
This package is explicitly for Celery 3.x–4.x only and the README opens with a request for a sponsor to update it — that's the project admitting it's unmaintained for modern use. Anyone on Celery 5.x (released 2020) should not install this; the official docs already cover Django integration without it. The single migration file and no subsequent migrations mean the DB schema hasn't evolved in years. The `celerycam`, `celerymon`, and `djcelerymon` management commands reference tooling that was deprecated and removed from Celery long ago, so half the management commands in the tree are dead weight.
We read the README, the directory tree and a key source file in June 2026. Nobody pays to be listed. How we judge →