Message247807
| Author |
vstinner |
| Recipients |
Yury.Selivanov, alex.gronholm, gvanrossum, scoder, vstinner, yselivanov |
| Date |
2015年08月01日.12:24:29 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAMpsgwZ9bJr2=XZ3kdmqPdChyA2n-+a6wQfZi3=DB7UMRPwSsQ@mail.gmail.com> |
| In-reply-to |
<1438424125.19.0.879160158112.issue24383@psf.upfronthosting.co.za> |
| Content |
There are other implementations of asyncio than the one in CPython.
Pulsar and Tornado define their own Task class. The greenio project
also has a special task object. aioeventlet and aiogevent may also
benefit from a way to register new "awaitable" things.
I'm not opposed to support concurrent.futures.Future object. I don't
like the idea of starting to add a special case for one module. Others
may want to do the same for their library. |
|