redis-py pexpire api inconsistency (Fix)

The Fix

pip install redis==7.1.0

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

Open PR/Commit

@@ -618,7 +618,8 @@ class Redis(RedisModuleCommands, CoreCommands, object):
     RESPONSE_CALLBACKS = {
         **string_keys_to_dict(
-            'AUTH COPY EXPIRE EXPIREAT HEXISTS HMSET LMOVE BLMOVE MOVE '
+            'AUTH COPY EXPIRE EXPIREAT PEXPIRE PEXPIREAT '
+            'HEXISTS HMSET LMOVE BLMOVE MOVE '

fix.md

Option A — Upgrade to fixed release\npip install redis==7.1.0\nWhen NOT to use: This fix should not be applied if the boolean parsing behavior is not desired.\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: The `pexpire` command was not parsing its response as a boolean, unlike `expire`
Why the fix works: Adds boolean parsing to the PEXPIRE and PEXPIREAT commands to ensure consistent behavior with the EXPIRE command. (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

Shows up under Python 3.5.1 in real deployments (not just unit tests).
The `pexpire` command was not parsing its response as a boolean, unlike `expire`
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: #1664
Fix PR: https://github.com/redis/redis-py/pull/1665
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.63

Discussion

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

Jump to Sources Open on GitHub

“@WisdomPill As always, thanks a tonne for reporting this - including the helpful link to the django-redis issue”

@chayim · 2021-11-01 · source

Failure Signature (Search String)

**Description**: Description of your issue, stack traces from errors and code that reproduces the issue
Uhoh, be careful what you wish for! Seriously though, I assigned it to you, since you asked ;). redis/client.py would use the changes in the RESPONSE_CALLBACKS. Those two commands

Copy-friendly signature

signature.txt

Failure Signature
-----------------
**Description**: Description of your issue, stack traces from errors and code that reproduces the issue
Uhoh, be careful what you wish for! Seriously though, I assigned it to you, since you asked ;). redis/client.py would use the changes in the RESPONSE_CALLBACKS. Those two commands don't currently have int mappings.

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
**Description**: Description of your issue, stack traces from errors and code that reproduces the issue
Uhoh, be careful what you wish for! Seriously though, I assigned it to you, since you asked ;). redis/client.py would use the changes in the RESPONSE_CALLBACKS. Those two commands don't currently have int mappings.

Environment

Python: 3.5.1

What Broke

Inconsistent behavior between `expire` and `pexpire` led to unexpected results in application logic.

Why It Broke

The `pexpire` command was not parsing its response as a boolean, unlike `expire`

Fix Options (Details)

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

pip install redis==7.1.0

When NOT to use: This fix should not be applied if the boolean parsing behavior is not desired.

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

First fixed release: 7.1.0

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

When NOT to Use This Fix

This fix should not be applied if the boolean parsing behavior is not desired.

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.