[Async-sig] asyncio <-> twisted interoperability

[Glyph]

> On Jun 3, 2016, at 19:17, Yury Selivanov <yselivanov at gmail.com> wrote:
> 
> In fact, I’m thinking now that Tornado/Twisted should keep their callbacks scheduling logic as is, and asyncio should keep its current implementation.

I have to agree.  There are are good reasons for both the asyncio and the Twisted ways of doing things, and they have subtly different priorities that cascade out into pretty much every application; changing it might cause things to break in more or less arbitrary ways.

>> +1 for replacing isinstance checks with an attribute that Twisted can add to Deferreds.
>> +1 for Ben’s suggestion that we should avoid ‘asyncio’ in the name here. __isfuture__?
> 
> Yes, an asyncio-agnostic name would be better.  I like __isfuture__.

__futuristic__? :)

-glyph