Skip to content
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

set_multi, get_multi, delete_multi raise KeyError when used with tuple keys #154

Closed
sergiimk opened this issue Nov 30, 2018 · 0 comments · Fixed by #155
Closed

set_multi, get_multi, delete_multi raise KeyError when used with tuple keys #154

sergiimk opened this issue Nov 30, 2018 · 0 comments · Fixed by #155

Comments

@sergiimk
Copy link
Contributor

We are relying on feature that allows specifying keys as tuples (hashvalue, key).

After upgrading from version 1.43 to 1.59 the *_multi methods started railing KeyError when used with tuple keys.

I traced this problem down to this line which seemingly unnecessarily mutates the orig_key, that makes the original key not present in resulting prefixed_to_orig_key.

sergiimk added a commit to sergiimk/python-memcached that referenced this issue Nov 30, 2018
sergiimk added a commit to sergiimk/python-memcached that referenced this issue Nov 30, 2018
sergiimk added a commit to sergiimk/python-memcached that referenced this issue Nov 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant