crenwick added the comment: 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! ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30098> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
