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 yselivanov
Recipients crenwick, yselivanov
Date 2017-04-18.23:06:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1492556820.01.0.212910589034.issue30098@psf.upfronthosting.co.za>
In-reply-to
Content
> A verbose error like this one would have made this behavior more clear to me.

Well, it already raises a TypeError with a clear message -- this is how we tell the user that the argument type is not supported in Python.  I don't think we need to specialize this code any further.

Instead I'd suggest to try to improve asyncio documentation for `ensure_future` and `run_coroutine_threadsafe`.
History
Date User Action Args
2017-04-18 23:07:00yselivanovsetrecipients: + yselivanov, crenwick
2017-04-18 23:07:00yselivanovsetmessageid: <1492556820.01.0.212910589034.issue30098@psf.upfronthosting.co.za>
2017-04-18 23:07:00yselivanovlinkissue30098 messages
2017-04-18 23:06:59yselivanovcreate