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 crenwick
Recipients crenwick, yselivanov
Date 2017-04-18.23:45:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1492559145.11.0.288123202077.issue30098@psf.upfronthosting.co.za>
In-reply-to
Content
Totally understandable. Some final thoughts:

> this is the first time I see somebody tries to use `ensure_future` on `run_coroutine_threadsafe` result, which suggests that it's not a common problem.

 - I wonder how much self-reporting will be done here.

 - I also considered making the existing error message more verbose (I think that still could be effective). However, I decided to open this PR as a separate TypeError to not muddle the language of the probably more common TypeError.

Thanks for your time and insight, Yury!
History
Date User Action Args
2017-04-18 23:45:45crenwicksetrecipients: + crenwick, yselivanov
2017-04-18 23:45:45crenwicksetmessageid: <1492559145.11.0.288123202077.issue30098@psf.upfronthosting.co.za>
2017-04-18 23:45:45crenwicklinkissue30098 messages
2017-04-18 23:45:45crenwickcreate