The future of peewee-async & Looking for maintenance

This project was started to experiment with async ORM interface. Our dev team has been using this in several small to mid-scale projects in production. But actually we didn’t have chance to build some large-scale solution for high loads with it. Right now, peewee-async is used in couple of projects in maintenace mode but not developed actively because of no current business needs and tight resources.

So, I’d want to ask the community: Would somebody want to take on/help with the future development and/or maintenance?

In the recent years more good practices in asyncio interfaces were developed. Also, peewee itself is becoming more developed and also changing it’s internals, so keeping up will be another challenge.

Not to mention, peewee’s author itself recommends just using Gevent 😃 http://docs.peewee-orm.com/en/latest/peewee/database.html#async-with-gevent

I’m thinking that peewee-async could be a good fit for some modern async framework. Also seeing the trend to go serverless apps, and ASGI support is possible there https://github.com/erm/mangum

Thoughts?

[rudyryk]

@kalombos sorry for the long response, check the invite

[kalombos]

@rudyryk could you make me as a collaborator on pypi? I have added github CI and merged a bugfix for the project and i am going to merge another bugfix and upload the first own release 😃