any plan to support async/await
Discussed and dismissed many times, notably #263. There are so many things I dislike about the ~twisted~ asyncio approach, mostly the fact that you have to write "asyncio"-specific everything -- drivers, ORMs, application frameworks, etc., etc. and even then you still have a "[what color is my function](https://journal.stuffwithstuff.com/2015/02/01/what-color-is-your-function/)" situation.

Use gevent. Seriously. You can thank me later. A commenter suggested [tortoise orm](https://tortoise-orm.readthedocs.io/en/latest/) - I cannot vouch for it, but wanted to preserve the recommendation for anyone who arrives here via google. @coleifer it's very sad that you ignore the `async/await` syntax. A lot of people/products use it these days and it's not only about `asyncio`. I know about the tortoise ORM, but I prefer Peewee syntax.

Maybe we have a chance to split the Peewee ORM and make a code that working with DB connections independently. So there will be drivers independent Peewee part which one only is responsible for the conversation Models <-> SQL and another part that implement database connection management. That way people could be available to use Peewee with any sync/async drivers. @klen - I wouldn't say that I ignore it, but I do not like the approach (for a number of reasons) and prefer the gevent approach for Python. The main reason I dislike it is because it requires a special "asyncio-aware" version of every piece of software in the stack.

This project exists, which might prove useful for people finding this issue in the future:

https://github.com/05bit/peewee-async As an alternative, there is another library: https://github.com/klen/peewee-aio
as the title. Thanks, team