The Fix
pip install redis==7.1.0
Based on closed redis/redis-py issue #2700 · 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%.
@@ -34,7 +34,7 @@
'importlib-metadata >= 1.0; python_version < "3.8"',
'typing-extensions; python_version<"3.8"',
- 'async-timeout>=4.0.2; python_version<="3.11.2"',
+ 'async-timeout>=4.0.2; python_full_version<="3.11.2"',
],
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: **Description**: Description of your issue, stack traces from errors and code that reproduces the issue
- Mechanism: Updates the dependency requirement for async-timeout to use python_full_version for Python 3.11.3 compatibility.
- Why the fix works: Updates the dependency requirement for async-timeout to use python_full_version for Python 3.11.3 compatibility. (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.11.3 in real deployments (not just unit tests).
- Production symptom (often without a traceback): **Description**: Description of your issue, stack traces from errors and code that reproduces the issue
Proof / Evidence
- GitHub issue: #2700
- Fix PR: https://github.com/redis/redis-py/pull/2699
- First fixed release: 7.1.0
- Reproduced locally: No (not executed)
- Last verified: 2026-02-07
- Confidence: 0.85
- Did this fix it?: Yes (upstream fix exists)
- Own content ratio: 0.65
Discussion
High-signal excerpts from the issue thread (symptoms, repros, edge-cases).
“async-timeout is not a requirement of Redis when used with Python 3.11.3 anymore. Your Pipfile.lock seems out of sync.”
“Maybe related to https://github.com/redis/redis-py/pull/2699”
“I should have mentioned that the redis code seems to still attempt to import the library, so loading the redis library fails without this library.”
Failure Signature (Search String)
- **Description**: Description of your issue, stack traces from errors and code that reproduces the issue
- `async-timeout` is not a requirement of Redis when used with Python 3.11.3 anymore. Your Pipfile.lock seems out of sync.
Copy-friendly signature
Failure Signature
-----------------
**Description**: Description of your issue, stack traces from errors and code that reproduces the issue
`async-timeout` is not a requirement of Redis when used with Python 3.11.3 anymore. Your Pipfile.lock seems out of sync.
Error Message
Signature-only (no traceback captured)
Error Message
-------------
**Description**: Description of your issue, stack traces from errors and code that reproduces the issue
`async-timeout` is not a requirement of Redis when used with Python 3.11.3 anymore. Your Pipfile.lock seems out of sync.
Environment
- Python: 3.11.3
What Broke
Loading the redis library fails without async-timeout, causing application errors.
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/2699
First fixed release: 7.1.0
Last verified: 2026-02-07. 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.
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.