redis-py error in set when ex is a float is confusing (Fix)

The Fix

pip install redis==7.1.0

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

@@ -1174,12 +1174,18 @@ def set(self, name, value,
             if isinstance(ex, datetime.timedelta):
                 ex = int(ex.total_seconds())
-            pieces.append(ex)
+            if isinstance(ex, int):
+                pieces.append(ex)

repro.py

>> import redis
>> r = redis.Redis(host='localhost', port=6379, db=0)
>> r.set('foo', 'bar', ex=10.0)
Traceback (most recent call last):
  File "/redis/client.py", line 1801, in set
    return self.execute_command('SET', *pieces)
  File "/redis/client.py", line 901, in execute_command
    return self.parse_response(conn, command_name, **options)
  File "/redis/client.py", line 915, in parse_response
    response = connection.read_response()
  File "/redis/connection.py", line 756, in read_response
    raise response
redis.exceptions.ResponseError: value is not an integer or out of range

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 should not be used if backward compatibility with older versions is required.\n\n

Why This Fix Works in Production

Trigger: >> import redis
Mechanism: The 'ex' parameter in the set method was not validated for integer type, causing confusion
Why the fix works: Enables the use of floating point numbers for the 'ex' and 'px' parameters in the SET command, addressing the issue where a float would raise an error. (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.7.3 in real deployments (not just unit tests).
The 'ex' parameter in the set method was not validated for integer type, causing confusion
Surfaces as: >> import redis

Proof / Evidence

GitHub issue: #1576
Fix PR: https://github.com/redis/redis-py/pull/1635
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.45

Discussion

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

Jump to Sources Open on GitHub

“**Version**: redis-py 3.5.3 **Platform**: Python 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0] on linux **Description**: This exception is confusing, because it doesn't specify which value is supposed to be an integer. There is a param”

Issue thread · issue description · source

Failure Signature (Search String)

>> import redis

Error Message

Stack trace

error.txt

Error Message
-------------
>> import redis
>> r = redis.Redis(host='localhost', port=6379, db=0)
>> r.set('foo', 'bar', ex=10.0)
Traceback (most recent call last):
  File "/redis/client.py", line 1801, in set
    return self.execute_command('SET', *pieces)
  File "/redis/client.py", line 901, in execute_command
    return self.parse_response(conn, command_name, **options)
  File "/redis/client.py", line 915, in parse_response
    response = connection.read_response()
  File "/redis/connection.py", line 756, in read_response
    raise response
redis.exceptions.ResponseError: value is not an integer or out of range

Minimal Reproduction

repro.py

>> import redis
>> r = redis.Redis(host='localhost', port=6379, db=0)
>> r.set('foo', 'bar', ex=10.0)
Traceback (most recent call last):
  File "/redis/client.py", line 1801, in set
    return self.execute_command('SET', *pieces)
  File "/redis/client.py", line 901, in execute_command
    return self.parse_response(conn, command_name, **options)
  File "/redis/client.py", line 915, in parse_response
    response = connection.read_response()
  File "/redis/connection.py", line 756, in read_response
    raise response
redis.exceptions.ResponseError: value is not an integer or out of range

Environment

Python: 3.7.3

What Broke

Users experienced confusing errors when passing float values to the 'ex' parameter.

Why It Broke

The 'ex' parameter in the set method was not validated for integer type, causing confusion

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 used if backward compatibility with older versions is required.

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

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 used if backward compatibility with older versions is required.

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.