We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As for now, at least official ban plugin is stuck at redis-py 2. Using redis-py 3 raises this exception: https://gist.github.com/lonewulfa/178842cc31276270548c5ad5060399c1
Breaking changes: https://github.com/redis/redis-py/blob/3a121bef7bbc5bb5f07b119b0eef2f7527a38eda/CHANGES#L539-L570
Probably good idea is adding compatibilty layer in minqlx itself.
The text was updated successfully, but these errors were encountered:
Redis3 had an upgrade description: https://pypi.org/project/redis3/
Mainly this affects redis.zadd and redis.zincrby calls. Backward compability would be useful as well. I mainly solved this in existing plugins with:
if redis.VERSION >= (3, ): # redis 3 calls else: # redis 2 calls
Sorry, something went wrong.
No branches or pull requests
As for now, at least official ban plugin is stuck at redis-py 2.
Using redis-py 3 raises this exception:
https://gist.github.com/lonewulfa/178842cc31276270548c5ad5060399c1
Breaking changes: https://github.com/redis/redis-py/blob/3a121bef7bbc5bb5f07b119b0eef2f7527a38eda/CHANGES#L539-L570
Probably good idea is adding compatibilty layer in minqlx itself.
The text was updated successfully, but these errors were encountered: