The Fix
pip install redis==7.1.0
Based on closed redis/redis-py issue #3174 · PR/commit linked
Production note: Most teams hit this during upgrades or environment changes. Roll out with a canary and smoke critical endpoints (health, OpenAPI/docs) before 100%.
@@ -36,7 +36,7 @@
python_requires=">=3.8",
install_requires=[
- 'async-timeout>=4.0.3',
+ 'async-timeout>=4.0.3; python_full_version<"3.11.3"',
],
Updating dependencies
Resolving dependencies... (11.4s)
Package operations: 1 install, 4 updates, 0 removals
• Updating python-dateutil (2.8.2 -> 2.9.0.post0)
• Installing async-timeout (4.0.3)
• Updating pydantic (2.6.2 -> 2.6.3)
• Updating email-validator (2.1.0.post1 -> 2.1.1)
• Updating redis (5.0.1 -> 5.0.2)
Writing lock file
Re-run the minimal reproduction on your broken version, then apply the fix and re-run.
Option A — Upgrade to fixed release\npip install redis==7.1.0\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: Redundant async-timeout dependency in Redis 5.0.2
- Mechanism: The async-timeout dependency was re-added unnecessarily for modern Python versions
- Why the fix works: Removed the redundant async-timeout dependency for modern Python versions. (first fixed release: 7.1.0).
- 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
- Shows up under Python 3.12.2 in real deployments (not just unit tests).
- The async-timeout dependency was re-added unnecessarily for modern Python versions
- Production symptom (often without a traceback): Redundant async-timeout dependency in Redis 5.0.2
Proof / Evidence
- GitHub issue: #3174
- Fix PR: https://github.com/redis/redis-py/pull/3177
- First fixed release: 7.1.0
- Reproduced locally: No (not executed)
- Last verified: 2026-02-09
- Confidence: 0.75
- Did this fix it?: Yes (upstream fix exists)
- Own content ratio: 0.59
Discussion
High-signal excerpts from the issue thread (symptoms, repros, edge-cases).
“Attaching log from updating redis 5.0.1 to 5.0.2 on Python 3.12.2.”
“@Zaczero Thanks for reporting this. I think you are right but I got a bit confused. How do you think it need to be now?…”
“Yes, totally make sense, thank you! Do you want to fix it or want me to do it?”
“I usually avoid doing such small PRs but suree https://github.com/redis/redis-py/pull/3177. Heads up, I did not complete the checklist.”
Failure Signature (Search String)
- Redundant async-timeout dependency in Redis 5.0.2
- The `async-timeout` dependency was originally removed in https://github.com/redis/redis-py/pull/2602 due to its redundancy in modern Python.
Copy-friendly signature
Failure Signature
-----------------
Redundant async-timeout dependency in Redis 5.0.2
The `async-timeout` dependency was originally removed in https://github.com/redis/redis-py/pull/2602 due to its redundancy in modern Python.
Error Message
Signature-only (no traceback captured)
Error Message
-------------
Redundant async-timeout dependency in Redis 5.0.2
The `async-timeout` dependency was originally removed in https://github.com/redis/redis-py/pull/2602 due to its redundancy in modern Python.
Minimal Reproduction
Updating dependencies
Resolving dependencies... (11.4s)
Package operations: 1 install, 4 updates, 0 removals
• Updating python-dateutil (2.8.2 -> 2.9.0.post0)
• Installing async-timeout (4.0.3)
• Updating pydantic (2.6.2 -> 2.6.3)
• Updating email-validator (2.1.0.post1 -> 2.1.1)
• Updating redis (5.0.1 -> 5.0.2)
Writing lock file
Environment
- Python: 3.12.2
What Broke
Users experienced installation issues due to the redundant async-timeout dependency.
Why It Broke
The async-timeout dependency was re-added unnecessarily for modern Python versions
Fix Options (Details)
Option A — Upgrade to fixed release Safe default (recommended)
pip install redis==7.1.0
Use when you can deploy the upstream fix. It is usually lower-risk than long-lived workarounds.
Fix reference: https://github.com/redis/redis-py/pull/3177
First fixed release: 7.1.0
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
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
- Make timeouts explicit and test them (unit + integration) to avoid silent behavior changes.
- Instrument retries (attempt count + reason) and alert on spikes to catch dependency slowdowns.
Version Compatibility Table
| Version | Status |
|---|---|
| 7.1.0 | Fixed |
Related Issues
No related fixes found.
Sources
We don’t republish the full GitHub discussion text. Use the links above for context.