Open ac130kz opened 3 months ago
I don't think it's necessary. At least for now. Because valkey and other technologies as a KeyDB are basically drop-in replacements for redis. The taskiq-redis is not affected by this issue, since the underlying library still has an MIT license and can be used without any issue.
Understandable, it's just that taskiq-redis has a hard dependency on redis-py. The problem that I see in the nearest year or so is compatibility with official redis is going to be less and less of the concern of fork maintainers. Well, I guess we have to wait and see.
Hi, I second this request. While it may be a drop-in placement for now redis and valkey will most likely diverge. And it seems like ValKey is the alternative that is been pushed forward the most compared to the other redis forks. Since bigger companies are investing into it
As you all probably know, Redis has changed its license, giving major corporations and contributors all the incentive to make a move to Linux Foundation's new project Valkey. So far the migration to
valkey-py
process seems to be quite straightforward, so I wonder, if it would be possible to implement its support.