delta/python-packages/redis-py.git, branch v3-breaking-changes

raise a LockError when the context manager fails to acquire a lock

2018-11-15T01:53:01+00:00

Fixes #621
Fixes #927

only support LuaLock going forward

2018-11-15T00:41:42+00:00

Everyone is using Redis 2.6 or greater, right? The Lua lock implementation
is so much nicer and less buggy.

Fixes #1031
Fixes #902
Fixes #793
Fixes #610

all commands should be able to accept bytes or strings for key names

2018-11-15T00:16:01+00:00

fixes #965

list_or_args should always create a new list

2018-11-15T00:13:03+00:00

use str() to encode int or long values

2018-11-14T23:42:28+00:00

on python2.7, repr() on a long produces '123L', which is clearly not what
we want

raise DataError instead of RedisError for user input problems

2018-11-14T23:17:30+00:00

This should be backwards compatible since DataError is a subclass of
RedisError.

only accept bytes, strings, ints, longs and floats as user input

2018-11-14T22:53:40+00:00

All input sent to Redis is coerced into bytes. This includes key names and
values. Prior to this change, redis-py made an effort to cooerce all input
into strings by calling str() (Python 3) or unicode() (Python 2). While this
works for a handful of types like ints, longs and floats, it fails for other
types like bools ('True' or 'False'), None ('None') and many user defined
types.

Starting with redis-py version 3.0, sending input of any other type is
considered an error an a DataError exception will be raised.

Fixes #471
Fixes #472
Fixes #321
Fixes #190

fix order of zincrby args to match redis server

2018-11-14T20:29:14+00:00

fixes #571

remove legacy Redis class

2018-11-14T00:44:36+00:00

redis-py maintained backwards compatibility by keeping the old "Redis"
class around for quite some time. While no doubt a convenience for folks
who relied on it, the presence of both Redis and StrictRedis causes
a number of support issues and general confusion. With 3.0, we're
breaking a few things to make redis-py better going forward.

This change removes the old Redis class. We also renamed the StrictRedis
class to Redis and aliased StrictRedis to Redis. For people that have
been using StrictRedis, this should not change anything. You can continue
doing things as you are.

People still using the legacy Redis class will need to update the argument
order for the SETEX, LREM and ZADD commands. Additionally, the return values
for TTL and PTTL now return the integer values -1 when a key exists but
has no expire time and -2 when a key does not exist. Previously these
cases returned a None value in the Redis class.

force mapping to be a single dict object on MSET, MSETNX and ZADD

2018-11-13T23:31:18+00:00

Previously MSET, MSETNX and ZADD accepted multiple ways to specify the
mapping of keys to values including via **kwargs. This turned out to be
a poor choice. As Redis evolved and added additional options to the ZADD
command, these options couldn't be specified in redis-py without possible
element name conflictd. This fixes that going forward and makes the commands
simpler.