Message244818
| Author | yselivanov |
|---|---|
| Recipients | alex.gronholm, asvetlov, gvanrossum, ncoghlan, python-dev, scoder, vstinner, yselivanov |
| Date | 2015-06-04.13:06:12 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1433423172.24.0.124792942599.issue24017@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> Hmm, but IMHO a) the new syntax isn't just for asyncio and b) awaiting a Future seems like a *very* reasonable thing to do. I think opening a new ticket for this is a good idea. Stefan, I honestly have bo idea what concurrent.Future.__await__ would do. There is no loop for concurrent module. If you have a patch with tests in mind, please open a separate issue (targeting 3.6). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-06-04 13:06:12 | yselivanov | set | recipients: + yselivanov, gvanrossum, ncoghlan, scoder, vstinner, asvetlov, alex.gronholm, python-dev |
| 2015-06-04 13:06:12 | yselivanov | set | messageid: <1433423172.24.0.124792942599.issue24017@psf.upfronthosting.co.za> |
| 2015-06-04 13:06:12 | yselivanov | link | issue24017 messages |
| 2015-06-04 13:06:12 | yselivanov | create | |