AsyncEase: Python Async Integration Suite

I really wish the community had coalesced around gevent.- no async/await, instead every possible thing that could block in the standard library is monkey-patched to yield to an event loop- this means that you can write the same exact code for synchronous and concurrent workflows, and immediately get levels of concurrency only bounded by memory limits- you'll never accidentally use a synchronous API in an async context and block your entire event loop (well, you can, if you spin on a tight CPU-bound loop, but that's a problem in asyncio too)- the ecosystem doesn't need to implement libraries fo

The async/await model gaining traction makes me really sad. I use it all the time and it just seems like a giant hack, a band-aid to hide "scary complexity" from the developers. A typical Microsoft approach to things, but it should stay there.First issue - the necessity for at least two of each method: "DoSomething" and "DoSomethingAsync". Weak. Now as a library developer, you just doubled your work. Sure, sometimes one method could wrap the other. But it's still weak sauce.I much prefer the Go model - you only code "sync" API's, and let the consumer of your API wrap it in a go-routine and mak