Message247817
| Author | alex.gronholm |
|---|---|
| Recipients | Yury.Selivanov, alex.gronholm, gvanrossum, scoder, vstinner, yselivanov |
| Date | 2015-08-01.19:04:38 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1438455878.44.0.262366784161.issue24383@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I agree with Stefan and Yury. As for the tests, Yury seemed to have those in his patches -- I'll take a look and see if they're directly applicable. For Python 3.5 and earlier, there is a workaround to awaiting for concurrent Futures, but it requires the use of the undocumented wrap_future() function. It is the fact that it's undocumented that bothers me. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-08-01 19:04:38 | alex.gronholm | set | recipients: + alex.gronholm, gvanrossum, scoder, vstinner, Yury.Selivanov, yselivanov |
| 2015-08-01 19:04:38 | alex.gronholm | set | messageid: <1438455878.44.0.262366784161.issue24383@psf.upfronthosting.co.za> |
| 2015-08-01 19:04:38 | alex.gronholm | link | issue24383 messages |
| 2015-08-01 19:04:38 | alex.gronholm | create | |