Connection pooling can be messed up by select()

[enaeseth]

The following sequence of commands poses a problem for redis-py. It is a reduction of a real sequence of commands invoked by a copy script I wrote, and needless to say, figuring out the behavior in the comments confused me mightily.

 from redis import Redis
 source = Redis(db=0) # source opens a new connection to localhost/0
 dest = Redis(db=0)   # dest uses the existing connection to localhost/0
 source.select(1)     # since source and dest are sharing a connection,
                      # they will now both operate on database 1

 copy(source, dest)   # doesn't accomplish anything useful!

[andymccurdy]

Definitely a bug. I think it makes sense for .select() to swap the underlying connection for the instance .select() is called on. I'll play with it a bit and make sure it makes sense from a usability perspective.

[andymccurdy]

This problem has been resolved in the "newapi" branch of redis-py. I plan on merging this branch with master in the next day or so and making an official release.

[andymccurdy]

This issue has been resolved in the 1.34 release of redis-py.