-
Notifications
You must be signed in to change notification settings - Fork 74
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
Future and roadmap of asyncio-redis #134
Comments
|
Adding mypy support will require completely redesigning how the Sphinx documentation for protocol.py works. 😭 |
Hi there, chiming in since I'm using python with asyncio too. Historically I used this library, but then moved to aioredis because I needed redis stream support, which wasn't supported (that was around April). Now I'm trying to get redis cluster working, which isn't supported in aioredis. I have found a library called aredis which support streams and redis cluster, but I also found some bugs with it for which I've made some pull requests. aioredis has a lot of users but isn't super maintained either. Not sure where I'm going with this but sharing in case people are looking for links / options. |
@bsergean : Thanks for sharing! @crusaderky : I know... I do regret the way type annotations are used in asyncio-redis. This dates from the time that Mypy did not yet exist. |
Also they will break in Python 4.0 with PEP 563 https://www.python.org/dev/peps/pep-0563/ |
Let's use this issue to discuss the future development of asyncio-redis.
As mentioned in the README:
A few things I think can/should be done:
The text was updated successfully, but these errors were encountered: