Status of this project?

[Graeme22]

Things to check first

• I have searched the existing issues and didn't find my feature already requested there

Feature description

Hello! I ran across this code as I was thinking about writing an anyio Redis client myself!

It seems like this library never made it out of the proof-of-concept stage? Or am I off base?

Use case

I’d be very interested in using a robust, simple Redis client with structured concurrency. redis-py has terrible typing, so I was considering forking it and removing all the sync code, then switching to structured concurrency (which should be relatively straightforward considering what the library does). However I don’t want to reinvent the wheel if unnecessary and it’d be good to collaborate too!

Let me know your thoughts @agronholm if this is something you’re still interested in working on. Appreciate a lot of your projects!

[agronholm]

I developed this project for use in a paid contract work which I no longer have. So this project fell into a limbo. Additionally, as part of another paid contract, I've made a PR against the official Python Redis client (here) to add AnyIO support. There were some architectural issues here, and our production deployment had problems when we tried to use this, so I had to roll back to the official Redis client. I never found out what the issue was, but it made me reluctant to use this library.

[Graeme22]

This is very helpful info, thanks!

The PR looks great! Unfortunately I doubt you'll get it merged anytime soon. redis-py doesn't even have good typing yet, so they probably won't have time for reviewing a 30k line PR!

Perhaps the PR could be turned into a fork? The sync code could be removed and the asyncio client replaced with anyio{asyncio,trio}. This would fix the typing issues as well.

[Graeme22]

For example this really basic issue has been open for 3 years now!

[agronholm]

I don't want to maintain a fork of something I strongly dislike. So either they merge that PR or I will be paid to finish this project. I don't see a lot of alternatives.

[Graeme22]

Fair enough! I may give the fork a try, appreciate the PR as a starting point!

[mm-andritz]

@agronholm, I remember you mentioning that you had some difficulties with this project (redis-anyio) in production. Do you remember of what were they?

[agronholm]

It's been a few years so I don't remember exactly, but I do remember we saw the number of processed requests go down, apparently something was getting stuck, and since this was in production, I didn't have a choice but to roll back rather than investigate in vivo. We never had issues in our staging environment.

[agronholm]

It's entirely possible that this was caused by bugs in upstream AnyIO, but we might never find out the truth.