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 Yury.Selivanov, gvanrossum, python-dev, r.david.murray, vstinner, vxgmichel, yselivanov
Date 2015-10-05.00:30:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Well, I still worry that this is just going to encourage more people to try and call awaitables from threaded code, and through some circuitous path of misunderstandings (probably involving StackOverflow :-) end up using this function.

(Pretty much the worst-case scenario would be calling run_coroutine_threadsafe() targeting the *current* loop, and then blocking the thread waiting for its result. Deadlock!)
Date User Action Args
2015-10-05 00:30:29gvanrossumsetrecipients: + gvanrossum, vstinner, r.david.murray, Yury.Selivanov, python-dev, yselivanov, vxgmichel
2015-10-05 00:30:29gvanrossumsetmessageid: <>
2015-10-05 00:30:29gvanrossumlinkissue25304 messages
2015-10-05 00:30:28gvanrossumcreate