Message244826
| Author | gvanrossum |
|---|---|
| Recipients | alex.gronholm, asvetlov, gvanrossum, ncoghlan, python-dev, scoder, vstinner, yselivanov |
| Date | 2015-06-04.15:05:57 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <CAP7+vJLTMJeJ3YWginWV5Nbe4aWnU7hT_1h_JK71_fEpLKSpZw@mail.gmail.com> |
| In-reply-to | <1433423172.24.0.124792942599.issue24017@psf.upfronthosting.co.za> |
| Content | |
|---|---|
Maybe it's possible to give an interpretation to awaiting on a threaded Future? __await__ could return a new asyncio Future, and add a completion callback to the original Future that makes the asyncio Future ready and transfers the result/exception. This would have to use loop.call_soon_threadsafe() to transfer control from the exector thread to the thread where the loop is running. The only thing I don't know is whether it's possible for __await__ to return a Future. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-06-04 15:05:57 | gvanrossum | set | recipients: + gvanrossum, ncoghlan, scoder, vstinner, asvetlov, alex.gronholm, python-dev, yselivanov |
| 2015-06-04 15:05:57 | gvanrossum | link | issue24017 messages |
| 2015-06-04 15:05:57 | gvanrossum | create | |