python-memcached warning is now out of date #475
Comments
|
@thenewguy Yes, It is fixed :) |
Closing |
|
@TysonAndre only have my phone at the moment but I don't think this is fixed per twemproxy/notes/recommendation.md Line 158 in 48e3f39 |
TysonAndre
added a commit
that referenced
this issue
Jul 2, 2021
https://github.com/linsomniac/python-memcached/ 1.5.8 had the delete_multi signature fixed in 2016. Anyone who had installed an outdated version should have seen this recommendation already or worked around it differently. There are a large number of other languages that have their own memcache clients with different bugs, don't continue linking to the workaround for an outdated python-memcached client version Closes #475
TysonAndre
added a commit
that referenced
this issue
Jul 2, 2021
https://github.com/linsomniac/python-memcached/ 1.5.8 had the delete_multi signature fixed in 2016. Anyone who had installed an outdated version should have seen this recommendation already or worked around it differently. There are a large number of other languages that have their own memcache clients with different bugs, don't continue linking to the workaround for an outdated python-memcached client version Closes #475
|
Oh. I thought you meant a warning emitted by python, not a docs warning to developers using that library. Didn't look at what |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have been reading about twemproxy for a python environment. I noticed your warning about python-memcached and investigated. It looks like this is now fixed per linsomniac/python-memcached@81cd83d
The text was updated successfully, but these errors were encountered: