This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients giampaolo.rodola, gvanrossum, pitrou, yselivanov
Date 2017-11-07.15:46:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1510069577.83.0.213398074469.issue31960@psf.upfronthosting.co.za>
In-reply-to
Content
The call_soon / call_soon_threadsafe distinction is not relevant to the problem I posted.  The problem is that the Future is registered with the event loop for the thread it was created in, even though it is only ever used in another thread (with another event loop).

Just try the snippet :-) If you want to see it finish in a finite time, move the future instantiation inside the coroutine.
History
Date User Action Args
2017-11-07 15:46:17pitrousetrecipients: + pitrou, gvanrossum, giampaolo.rodola, yselivanov
2017-11-07 15:46:17pitrousetmessageid: <1510069577.83.0.213398074469.issue31960@psf.upfronthosting.co.za>
2017-11-07 15:46:17pitroulinkissue31960 messages
2017-11-07 15:46:17pitroucreate