Skip to content

Future and roadmap of asyncio-redis #134

@jonathanslenders

Description

@jonathanslenders

Let's use this issue to discuss the future development of asyncio-redis.

As mentioned in the README:

Right now, this library is working fine, but not actively maintained, due to lack of time and shift of priorities on my side (Jonathan). Most of my time doing open source goes to prompt_toolkt community.

I still merge pull request when they are fine, especially for bug/security fixes. But for a while now, we don't have new features. If you are already using it, then there's not really a need to worry, asyncio-redis will keep working fine, and we fix bugs, but it's not really evolving.

If anyone is interested to seriously take over development, please let me know. Also keep in mind that there is a competing library called aioredis, which does have a lot of activity.

A few things I think can/should be done:

  • Drop Python 3.5 support.
  • Use proper type annotations and check the code base with mypy (the current use of type annotations dates from before mypy and is not really compatible).
  • Maybe apply a code formatter like Black.
  • Probably add more Redis commands.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions