The Fix
pip install redis==7.1.0
Based on closed redis/redis-py issue #1645 · 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%.
@@ -16,212 +16,218 @@
# add these directories to sys.path here. If the directory is relative to the
# documentation root, use os.path.abspath to make it absolute, like shown here.
-#sys.path.insert(0, os.path.abspath('.'))
+# sys.path.insert(0, os.path.abspath('.'))
sys.path.append(os.path.abspath(os.path.pardir))
Option A — Upgrade to fixed release\npip install redis==7.1.0\nWhen NOT to use: This fix should not be applied if the package structure is intentionally altered for other reasons.\n\n
Why This Fix Works in Production
- Trigger: .../site-packages/redis/client.py:9: in <module>
- Mechanism: The package was fixed to include the missing redis.commands module in the release.
- Why the fix works: The package was fixed to include the missing redis.commands module in the release. (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 in real deployments (not just unit tests).
- Surfaces as: .../site-packages/redis/client.py:9: in <module>
Proof / Evidence
- GitHub issue: #1645
- Fix PR: https://github.com/redis/redis-py/pull/1649
- 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.59
Discussion
High-signal excerpts from the issue thread (symptoms, repros, edge-cases).
“@guigarfr Wow - thanks for the great catch. A new package will have to upstream shortly. I'm not sure why setup didn't bulid the package…”
“For the curious - setup.py build/sdist didn't automatically descend into redis.commands. The change linked here adds redis.commands to the packages tree. A new release is…”
“It is marked as closed, but I'm still getting exactly the same error: !image”
“Ok, I have an extension that syncs .ipynb to .py files. It looks like that py file gets executed too when I do the import.…”
Failure Signature (Search String)
- .../site-packages/redis/client.py:9: in <module>
Error Message
Stack trace
Error Message
-------------
.../site-packages/redis/client.py:9: in <module>
from redis.commands import CoreCommands, RedisModuleCommands, list_or_args
E ModuleNotFoundError: No module named 'redis.commands'
Environment
- Python: 3.11
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/1649
First fixed release: 7.1.0
Last verified: 2026-02-07. Validate in your environment.
When NOT to Use This Fix
- This fix should not be applied if the package structure is intentionally altered for other reasons.
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 |
|---|---|
| 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.