Message247788
| Author | yselivanov |
|---|---|
| Recipients | Yury.Selivanov, alex.gronholm, gvanrossum, scoder, vstinner, yselivanov |
| Date | 2015-07-31.23:26:10 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1438385170.47.0.515175912412.issue24383@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> In short, I implemented support for concurrent.futures in the asyncio Task class instead of making concurrent.futures aware of asyncio. The __await__ implementation in concurrent.futures closely mirrors that of asyncio's Future. I like your approach and the proposed patch. I think we should commit this in 3.6 (the final patch should include docs & tests). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-07-31 23:26:10 | yselivanov | set | recipients: + yselivanov, gvanrossum, scoder, vstinner, alex.gronholm, Yury.Selivanov |
| 2015-07-31 23:26:10 | yselivanov | set | messageid: <1438385170.47.0.515175912412.issue24383@psf.upfronthosting.co.za> |
| 2015-07-31 23:26:10 | yselivanov | link | issue24383 messages |
| 2015-07-31 23:26:10 | yselivanov | create | |