Message247271
| Author | Yury.Selivanov |
|---|---|
| Recipients | Yury.Selivanov, alex.gronholm, gvanrossum, scoder, vstinner, yselivanov |
| Date | 2015-07-24.11:54:48 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <4F5BFBE0-04C3-4F95-B169-9E747093B0CF@gmail.com> |
| In-reply-to | <1437738307.26.0.0197959915604.issue24383@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> Any counterarguments?
There are no counterarguments. There is no obvious way to support concurrent.futures transparently, though:
await conc_fut
requires conc_fut to implement __await__.
So we either have to implement __await__ for concurrent futures and provide some kind of registry for frameworks, or we can implement a wrapper function:
await asyncio_compat(conc_fut)
Anyways, concrete ideas and API suggestions are welcome. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-07-24 11:54:48 | Yury.Selivanov | set | recipients: + Yury.Selivanov, gvanrossum, scoder, vstinner, alex.gronholm, yselivanov |
| 2015-07-24 11:54:48 | Yury.Selivanov | link | issue24383 messages |
| 2015-07-24 11:54:48 | Yury.Selivanov | create | |