This is like six, but for wrapping
over differences between Twisted and asyncio so one can write code
that runs unmodified on both (aka source code compatibility). In
other words: your users can choose if they want asyncio or Twisted
as a dependency.

Note that, with this approach, user code runs under the native event
loop of either Twisted or asyncio. This is different from attaching
either one’s event loop to the other using some event loop adapter.

Instead of directly importing, instantiating and using Deferred
(for Twisted) or Future (for asyncio) objects, txaio provides
helper-functions to do that for you, as well as associated things like
adding callbacks or errbacks.

This obviously changes the style of your code, but then you can choose
at runtime (or import time) which underlying event-loop to use. This
means you can write one code-base that can run on Twisted or
asyncio (without a Twisted dependency) as you or your users see fit.