redis-py `Script` class defined twice (Fix)

The Fix

pip install redis==7.1.0

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

Open PR/Commit

@@ -1,28 +0,0 @@
@@ -1,28 +0,0 @@
-[flake8]
-max-line-length = 88
-exclude =

fix.md

Option A — Upgrade to fixed release\npip install redis==7.1.0\nWhen NOT to use: Do not apply this fix if both definitions are intended for different contexts.\n\n

Why This Fix Works in Production

Trigger: This leads to potential confusion and errors when the class is referenced in the code.
Mechanism: Deletes the first-defined (and thus duplicate) `Script` class in `redis/commands/core.py`, resolving the issue of class redefinition.
Why the fix works: Deletes the first-defined (and thus duplicate) `Script` class in `redis/commands/core.py`, resolving the issue of class redefinition. (first fixed release: 7.1.0).

Production impact:

If left unfixed, retries/timeouts can trigger duplicate external side-effects (double charges, duplicate emails, repeated writes).

Why This Breaks in Prod

Production symptom (often without a traceback): This leads to potential confusion and errors when the class is referenced in the code.

Proof / Evidence

GitHub issue: #3332
Fix PR: https://github.com/redis/redis-py/pull/3147
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.84

Discussion

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

Jump to Sources Open on GitHub

“This would be caught by a linter such as Ruff: https://github.com/redis/redis-py/pull/3147 https://docs.astral.sh/ruff/rules/redefined-while-unused/”

@akx · 2024-09-24 · source

“> But then you would be using ruff. This is true. Is that a problem?”

@akx · 2024-09-25 · source

“I apologize, my comment just created disharmony and didn't contribute anything useful. Please disregard.”

@kurtmckee · 2024-09-25 · source

Failure Signature (Search String)

This leads to potential confusion and errors when the class is referenced in the code.

Copy-friendly signature

signature.txt

Failure Signature
-----------------
This leads to potential confusion and errors when the class is referenced in the code.

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
This leads to potential confusion and errors when the class is referenced in the code.

What Broke

This leads to potential confusion and errors when the class is referenced in the code.

Fix Options (Details)

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

pip install redis==7.1.0

When NOT to use: Do not apply this fix if both definitions are intended for different contexts.

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

First fixed release: 7.1.0

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

When NOT to Use This Fix

Do not apply this fix if both definitions are intended for different contexts.

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:duplicate-processing redis-py hub redis-py best practices All hubs All clusters

Related clusters: Configuration error Retry storm Data consistency

Sources

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