Message247786
| Author | alex.gronholm |
|---|---|
| Recipients | Yury.Selivanov, alex.gronholm, gvanrossum, scoder, vstinner, yselivanov |
| Date | 2015-07-31.23:16:23 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1438384584.03.0.258494501551.issue24383@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Sorry to keep you waiting. This sample code runs fine with the attached patch: https://gist.github.com/agronholm/43c71be0028bb866753a 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. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-07-31 23:16:24 | alex.gronholm | set | recipients: + alex.gronholm, gvanrossum, scoder, vstinner, Yury.Selivanov, yselivanov |
| 2015-07-31 23:16:24 | alex.gronholm | set | messageid: <1438384584.03.0.258494501551.issue24383@psf.upfronthosting.co.za> |
| 2015-07-31 23:16:24 | alex.gronholm | link | issue24383 messages |
| 2015-07-31 23:16:23 | alex.gronholm | create | |