The Fix
pip install celery==5.3.0rc1
Based on closed celery/celery issue #8078 · 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.
@@ -7,7 +7,6 @@
- raise :exc:`ValueError` instead of ``ParseError``
- return naive :class:`~datetime.datetime` by default
- - uses :class:`pytz.FixedOffset`
This is the original License:
Option A — Upgrade to fixed release\npip install celery==5.3.0rc1\nWhen NOT to use: This fix is not suitable for projects that require pytz for legacy compatibility.\n\n
Why This Fix Works in Production
- Trigger: - [x] I have included all related issues and possible duplicate issues in this issue
- Mechanism: The library was using pytz, which is deprecated in Django and needs replacement with zoneinfo
- Why the fix works: Deprecates pytz and replaces it with zoneinfo, addressing issue #8078. (first fixed release: 5.3.0rc1).
- If left unfixed, retries/timeouts can trigger duplicate external side-effects (double charges, duplicate emails, repeated writes).
Why This Breaks in Prod
- The library was using pytz, which is deprecated in Django and needs replacement with zoneinfo
- Production symptom (often without a traceback): - [x] I have included all related issues and possible duplicate issues in this issue
Proof / Evidence
- GitHub issue: #8078
- Fix PR: https://github.com/celery/celery/pull/8159
- First fixed release: 5.3.0rc1
- 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.73
Discussion
High-signal excerpts from the issue thread (symptoms, repros, edge-cases).
“Hey @wongcht :wave:, Thank you for opening an issue”
“ping me with your draft PR please when it is in progress”
“A bit busy now, but would be happy to work on addressing this over the coming week @auvipy!”
Failure Signature (Search String)
- - [x] I have included all related issues and possible duplicate issues in this issue
- or possible duplicates to this issue as requested by the checklist above.
Copy-friendly signature
Failure Signature
-----------------
- [x] I have included all related issues and possible duplicate issues in this issue
or possible duplicates to this issue as requested by the checklist above.
Error Message
Signature-only (no traceback captured)
Error Message
-------------
- [x] I have included all related issues and possible duplicate issues in this issue
or possible duplicates to this issue as requested by the checklist above.
What Broke
Using pytz may lead to compatibility issues with future Django versions, causing potential runtime errors.
Why It Broke
The library was using pytz, which is deprecated in Django and needs replacement with zoneinfo
Fix Options (Details)
Option A — Upgrade to fixed release Safe default (recommended)
pip install celery==5.3.0rc1
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/8159
First fixed release: 5.3.0rc1
Last verified: 2026-02-09. Validate in your environment.
When NOT to Use This Fix
- This fix is not suitable for projects that require pytz for legacy compatibility.
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.0rc1 | Fixed |
Related Issues
No related fixes found.
Sources
We don’t republish the full GitHub discussion text. Use the links above for context.