-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
redis-py 2.10 changed "errors" connection keyword argument to "encoding_errors" #40
Comments
Thanks for reporting! Going to pull in changes by @omidraha and test a couple different versions. Closing this one but you can follow activity on the master branch today/this weekend if interested. |
OK, tested this and was not able to reproduce. If you look at redis-py's latest master, it shows It uses encoding_errors internally (in its connection object), but the API exposed by Were you using the default redis callable or a custom one? I can't think of anyway you could get that error unless you had a setting for If you were not using a custom callable, can you share your redis session settings (minus secrets/cookie stuff/anything confidential) and the exact redis-py/pyramid/pyramid_redis_sessions versions? I'll re-open while I wait to hear back. Thanks! |
Good news! I reproduced the error. Looks like a bug in redis-py to me, since they only document one API for StrictRedis regardless of how you invoke it, but the behavior differs when you use I'm going to figure out the latest working version of redis-py and pin it to that for now. I don't want to make code changes to accommodate two different APIs if it's just a bug they introduced on this version. |
Going to close for now since PR #42 addresses this, but I'll follow the issue on the |
Thank you so much for looking into it! I apologize for leaving you hanging the last couple of days, but it looks like you got to the bottom of it. I've set my project requirements to redis==2.9.1 for the time being. |
The latest version of redis-py changed the keyword argument "errors" to "encoding_errorrs" resulting in the following error message when attempting to use
request.session
The text was updated successfully, but these errors were encountered: