You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To upgrade redis to 3.x we need to change the way we handle ttl in the session as per:
Upgrading from redis-py 2.X to 3.0
redis-py 3.0 introduces many new features but required a number of backwards incompatible changes to be made in the process. This section attempts to provide an upgrade path for users migrating from 2.X to 3.0.
Python Version Support
redis-py 3.0 now supports Python 2.7 and Python 3.4+. Python 2.6 and 3.3 support has been dropped.
Client Classes: Redis and StrictRedis
redis-py 3.0 drops support for the legacy "Redis" client class. "StrictRedis" has been renamed to "Redis" and an alias named "StrictRedis" is provided so that users previously using "StrictRedis" can continue to run unchanged.
The 2.X "Redis" class provided alternative implementations of a few commands. This confused users (rightfully so) and caused a number of support issues. To make things easier going forward, it was decided to drop support for these alternate implementations and instead focus on a single client class.
2.X users that are already using StrictRedis don't have to change the class name. StrictRedis will continue to work for the forseeable future.
2.X users that are using the Redis class will have to make changes if they use any of the following commands:
SETEX: The argument order has changed. The new order is (name, time, value).
LREM: The argument order has changed. The new order is (name, num, value).
TTL and PTTL: The return value is now always an int and matches the official Redis command (>0 indicates the timeout, -1 indicates that the key exists but that it has no expire time set, -2 indicates that the key does not exist)
The text was updated successfully, but these errors were encountered:
To upgrade redis to 3.x we need to change the way we handle ttl in the session as per:
The text was updated successfully, but these errors were encountered: