redis-py Misleading docstring of class `Redis` (Fix)

The Fix

pip install redis==7.1.0

Based on closed redis/redis-py issue #1442 · 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%.

Jump to Verify Open PR/Commit

@@ -613,8 +613,10 @@ class Redis(RedisModuleCommands, CoreCommands, object):
     and an implementation of the Redis protocol.
 
-    Connection and Pipeline derive from this, implementing how
-    the commands are sent and received to the Redis server
+    Pipelines derive from this, implementing how

repro.py

class Redis:
    """
    Implementation of the Redis protocol.

    This abstract class provides a Python interface to all Redis commands
    and an implementation of the Redis protocol.

    Connection and Pipeline derive from this, implementing how
    the commands are sent and received to the Redis server
    """

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 redis==7.1.0\nWhen NOT to use: This fix is not applicable if the class hierarchy changes in future versions.\n\n

Why This Fix Works in Production

Trigger: At least in terms of OOP (object-oriented programming), the class [`Connection`](https://github.com/andymccurdy/redis-py/blob/3.5.3/redis/connection.py#L497)…
Mechanism: The docstring of the Redis class inaccurately states that Connection derives from it
Why the fix works: Improved the docstring of the Redis class to clarify that only Pipelines derive from it, not Connections. (first fixed release: 7.1.0).

Production impact:

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

The docstring of the Redis class inaccurately states that Connection derives from it
Production symptom (often without a traceback): At least in terms of OOP (object-oriented programming), the class [`Connection`](https://github.com/andymccurdy/redis-py/blob/3.5.3/redis/connection.py#L497) *does not* derive from `Redis` since at least 2017.

Proof / Evidence

GitHub issue: #1442
Fix PR: https://github.com/redis/redis-py/pull/1675
First fixed release: 7.1.0
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.60

Verified Execution

We executed the runnable minimal repro in a temporary environment and captured exit codes + logs.

Status: PASS
Ran: 2026-02-11T16:52:29Z
Package: redis
Fixed: 7.1.0
Mode: fixed_only
Outcome: ok

Logs

affected (exit=None)

fixed (exit=0)

Discussion

High-signal excerpts from the issue thread (symptoms, repros, edge-cases).

Jump to Sources Open on GitHub

“My impression is that this docstring is misleading: At least in terms of OOP (object-oriented programming), the class Connection *does not* derive from Redis since at least 2017. (Pipeline, however, does.) This seems especially relevant as”

Issue thread · issue description · source

Failure Signature (Search String)

At least in terms of OOP (object-oriented programming), the class [`Connection`](https://github.com/andymccurdy/redis-py/blob/3.5.3/redis/connection.py#L497) *does not* derive

Copy-friendly signature

signature.txt

Failure Signature
-----------------
At least in terms of OOP (object-oriented programming), the class [`Connection`](https://github.com/andymccurdy/redis-py/blob/3.5.3/redis/connection.py#L497) *does not* derive from `Redis` since at least 2017.

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
At least in terms of OOP (object-oriented programming), the class [`Connection`](https://github.com/andymccurdy/redis-py/blob/3.5.3/redis/connection.py#L497) *does not* derive from `Redis` since at least 2017.

Minimal Reproduction

repro.py

class Redis:
    """
    Implementation of the Redis protocol.

    This abstract class provides a Python interface to all Redis commands
    and an implementation of the Redis protocol.

    Connection and Pipeline derive from this, implementing how
    the commands are sent and received to the Redis server
    """

What Broke

Misleading documentation led to incorrect assumptions about class relationships, causing integration issues.

Why It Broke

The docstring of the Redis class inaccurately states that Connection derives from it

Fix Options (Details)

Option A — Upgrade to fixed release Safe default (recommended)

pip install redis==7.1.0

When NOT to use: This fix is not applicable if the class hierarchy changes in future versions.

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/1675

First fixed release: 7.1.0

Last verified: 2026-02-09. Validate in your environment.

When NOT to Use This Fix

This fix is not applicable if the class hierarchy changes in future versions.

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
7.1.0	Fixed

Related Issues

No related fixes found.

Cluster: redis-py:configuration-error redis-py hub redis-py best practices All hubs All clusters

Related clusters: Retry storm Data consistency Race condition

Sources

We don’t republish the full GitHub discussion text. Use the links above for context.