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 gvanrossum
Recipients Ilya.Kulakov, gvanrossum, r.david.murray, vstinner, yselivanov
Date 2016-05-09.15:37:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJLpCwX22csFJ_9NQRVbHrzeG_EZsw9DMiyQpYEBB3Toiw@mail.gmail.com>
In-reply-to <1462807689.44.0.727248805042.issue26969@psf.upfronthosting.co.za>
Content
Instead of starting a new event loop, you should figure out a way to wait
for an event in the existing loop. IIUC that loop runs in a different
thread -- I think you can solve this by using a threading.Event that you
set from a wrapper coroutine running in your event loop and waited for in
the main loop. (If you're worried about blocking the event loop just to
acquire the threading lock that's part of threading.Event, you can use
run_in_executor().

Good luck!
History
Date User Action Args
2016-05-09 15:37:17gvanrossumsetrecipients: + gvanrossum, vstinner, r.david.murray, yselivanov, Ilya.Kulakov
2016-05-09 15:37:17gvanrossumlinkissue26969 messages
2016-05-09 15:37:17gvanrossumcreate