Celery django example does not run (Fix)

The Fix

pip install celery==5.5.0

Based on closed celery/celery issue #9431 · PR/commit linked

Production note: This usually shows up under retries/timeouts. Treat it as a side-effect risk until you can verify behavior with a canary + real traffic.

Jump to Verify Open PR/Commit

@@ -1,7 +1,5 @@
 import os
 
-from django.conf import settings
-
 from celery import Celery

repro.py

amqp==5.3.1
asgiref==3.8.1
billiard==4.2.1
celery==5.4.0
click==8.1.7
click-didyoumean==0.3.1
click-plugins==1.1.1
click-repl==0.3.0
Django==5.1.3
kombu==5.4.2
prompt_toolkit==3.0.48
python-dateutil==2.9.0.post0
six==1.16.0
SQLAlchemy==2.0.36
sqlparse==0.5.2
typing_extensions==4.12.2
tzdata==2024.2
vine==5.1.0
wcwidth==0.2.13

verify

Re-run: python ./manage.py shell

fix.md

Option A — Upgrade to fixed release\npip install celery==5.5.0\nWhen NOT to use: Do not apply this fix if the Django example is not being used.\n\n

Why This Fix Works in Production

Trigger: $ python ./manage.py shell
Mechanism: The import statement for settings in the Django example was incorrect, causing the example to fail
Why the fix works: Fixed the Django example to ensure it runs correctly by updating the import statement for settings. (first fixed release: 5.5.0).

Production impact:

If left unfixed, the same config can fail only in production (env differences), causing startup failures or partial feature outages.

Why This Breaks in Prod

The import statement for settings in the Django example was incorrect, causing the example to fail
Surfaces as: $ python ./manage.py shell

Proof / Evidence

GitHub issue: #9431
Fix PR: https://github.com/celery/celery/pull/9562
First fixed release: 5.5.0
Reproduced locally: No (not executed)
Last verified: 2026-02-09
Confidence: 0.85
Did this fix it?: Yes (upstream fix exists)
Own content ratio: 0.63

Discussion

High-signal excerpts from the issue thread (symptoms, repros, edge-cases).

Jump to Sources Open on GitHub

“I do not understand why the last change (#9099) was made at all”

@rmcloughlin · 2024-12-13 · source

“Hey @giovanniacg - it seems the last change (#9099) is causing some issues. Can you give it a look please?”

@Nusnus · 2024-12-12 · source

“> But even then the example code still fails to run. Exactly why I didn't revert it. Let's see if @giovanniacg is available to handle…”

@Nusnus · 2024-12-13 · source

“@auvipy any chance you can give it a look? Just try to follow the README for the Django example, step by step, and you should…”

@Nusnus · 2024-12-14 · source

Failure Signature (Search String)

$ python ./manage.py shell

Error Message

Stack trace

error.txt

Error Message
-------------
$ python ./manage.py shell
...
AttributeError: 'Settings' object has no attribute '__name__'. Did you mean: '__ne__'?

Minimal Reproduction

repro.py

amqp==5.3.1
asgiref==3.8.1
billiard==4.2.1
celery==5.4.0
click==8.1.7
click-didyoumean==0.3.1
click-plugins==1.1.1
click-repl==0.3.0
Django==5.1.3
kombu==5.4.2
prompt_toolkit==3.0.48
python-dateutil==2.9.0.post0
six==1.16.0
SQLAlchemy==2.0.36
sqlparse==0.5.2
typing_extensions==4.12.2
tzdata==2024.2
vine==5.1.0
wcwidth==0.2.13

What Broke

The Django example fails to run, leading to confusion for users trying to follow the README.

Why It Broke

The import statement for settings in the Django example was incorrect, causing the example to fail

Fix Options (Details)

Option A — Upgrade to fixed release Safe default (recommended)

pip install celery==5.5.0

When NOT to use: Do not apply this fix if the Django example is not being used.

Use when you can deploy the upstream fix. It is usually lower-risk than long-lived workarounds.

Fix reference: https://github.com/celery/celery/pull/9562

First fixed release: 5.5.0

Last verified: 2026-02-09. Validate in your environment.

When NOT to Use This Fix

Do not apply this fix if the Django example is not being used.

Verify Fix

verify

Re-run: python ./manage.py shell

Did This Fix Work in Your Case?

Quick signal helps us prioritize which fixes to verify and improve.

Prevention

Capture the exact failing error string in logs and tests so you can reproduce via a minimal script.
Pin production dependencies and upgrade only with a reproducible test that hits the failing path.

Version Compatibility Table

Version	Status
5.5.0	Fixed

Related Issues

No related fixes found.

Cluster: celery:configuration-error Celery hub Celery best practices All hubs All clusters

Related clusters: Data consistency Duplicates Duplicate processing

Sources

We don’t republish the full GitHub discussion text. Use the links above for context.