-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Seeking guidance for hiredis
dependency on redis-py
#3392
Comments
hiredis
dependency on reidis-py
hiredis
dependency on redis-py
I noticed that in the recent Including such a change in the release log would be quite helpful for other developers. |
So I request to add this information on release notes of 5.1.0 :) |
Hi @ramchandra-st, it's possible to use Which version of Regards, |
Hey guys, i created this issue #3393 about it, i just realised that this is talking about this same issue, should i close it? |
@helissonomc Yes, please. Can you add any relevant detail here please. |
With version 5.1.0 I started to face the error message:
If the hiredis version is lower than 3 (which mine is) the HIREDIS_AVAILABLE is going to be false, therefore it will keep giving error inside the redis/connection.py file, because the |
Yeah, problem presented by @helissonomc is same as what I want to highlight here. Thanks folks for engagement here :) |
OK, seems to be a bug that was introduced by trying to enforce hiredis >=3. We will take a look and fix it. Thanks for the detailed report. |
Hi, this bug could be reproduced with Regards, |
I have a question regarding the
hiredis
dependency inredis-py
.Is hiredis a required dependency for using the package, or is it optional?
I have an implicit dependency on
redis-py
and I've encountered an issue with a locked version ofhiredis
in myrequirements.txt
Since
redis-py
updates automatically as it is implicit, it can lead to a version mismatch whereredis-py
is updated, buthiredis
remains locked to an older version, causing an unsynchronized state.Could you provide guidance on how to handle this situation and avoid any conflicts arising from the version lock?
The text was updated successfully, but these errors were encountered: