Long-time Twisted user (and lover) here. Lots of what we build are fairly web-transaction data translators (http to http or http to db APIs). I find that async.io, by avoiding callbacks, allows us to create a more classical-looking code structure. It works for us.

That being said: a) the Twisted environment is extremely robust and battle tested. b) I know that after six months of writing async.io code I'm still just tipping my toe into the capabilities and have yet to fully wrap my head around the details. Would love to see one of those single-topic O'Reilly books take a deep dive into async.io details.

Pffft. Twisted core devs have embraced asyncio and have made Twisted play nice with asyncio. Do what makes sense.

>"But this is something that one cannot say aloud in many Python circles"

Can you explain why this is? What's the central issue?