The Fix
pip install celery==5.3.5
Based on closed celery/celery issue #8560 · PR/commit linked
@@ -75,7 +75,7 @@ jobs:
fail-fast: false
matrix:
- python-version: ['3.8', '3.9', '3.10', '3.11']
+ python-version: ['3.8', '3.9', '3.10', '3.11', '3.12']
toxenv: ['redis', 'rabbitmq', 'rabbitmq_redis']
repro.py
.. _version-x.y.z:
x.y.z
=====
:release-date: YYYY-MM-DD HH:MM P.M/A.M TimeZone
:release-by: Release Manager Name
Changes list in RST format.
verify
Re-run the minimal reproduction on your broken version, then apply the fix and re-run.
fix.md
Option A — Upgrade to fixed release\npip install celery==5.3.5\nWhen NOT to use: Do not use if it changes public behavior or if the failure cannot be reproduced.\n\n
Why This Fix Works in Production
- Trigger: - [x] Breaking Changes Validation
- Mechanism: Fixed CI Support with Python 3.12, ensuring compatibility and stability for the upcoming release.
- Why the fix works: Fixed CI Support with Python 3.12, ensuring compatibility and stability for the upcoming release. (first fixed release: 5.3.5).
Why This Breaks in Prod
- Shows up under Python 3.12 in real deployments (not just unit tests).
- Production symptom (often without a traceback): - [x] Breaking Changes Validation
Proof / Evidence
- GitHub issue: #8560
- Fix PR: https://github.com/celery/celery/pull/8611
- First fixed release: 5.3.5
- 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.64
Discussion
High-signal excerpts from the issue thread (symptoms, repros, edge-cases).
“two more package released! next I will try to fix the integration test of kombu on python 3.12”
“@auvipy hey there, any updates on the release 5.3.5? Updates on my part: Approximately by the end of November I plan to get the pytest-celery…”
“I forgot to update the release date! I added python 3.12 to some dependencies+ some tests needed to fix in the dependencies”
“Hopefully everything's fine again! (If yes, any news on the release? :))”
Failure Signature (Search String)
- - [x] Breaking Changes Validation
- - [x] Compile Changelog
Copy-friendly signature
signature.txt
Failure Signature
-----------------
- [x] Breaking Changes Validation
- [x] Compile Changelog
Error Message
Signature-only (no traceback captured)
error.txt
Error Message
-------------
- [x] Breaking Changes Validation
- [x] Compile Changelog
Minimal Reproduction
repro.py
.. _version-x.y.z:
x.y.z
=====
:release-date: YYYY-MM-DD HH:MM P.M/A.M TimeZone
:release-by: Release Manager Name
Changes list in RST format.
Environment
- Python: 3.12
Fix Options (Details)
Option A — Upgrade to fixed release Safe default (recommended)
pip install celery==5.3.5
When NOT to use: Do not use if it changes public behavior or if the failure cannot be reproduced.
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/8611
First fixed release: 5.3.5
Last verified: 2026-02-09. Validate in your environment.
When NOT to Use This Fix
- Do not use if it changes public behavior or if the failure cannot be reproduced.
Verify Fix
verify
Re-run the minimal reproduction on your broken version, then apply the fix and re-run.
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.3.5 | Fixed |
Related Issues
No related fixes found.
Sources
We don’t republish the full GitHub discussion text. Use the links above for context.