Message291851
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! |
|
Date |
User |
Action |
Args |
2017-04-18 23:45:45 | crenwick | set | recipients:
+ crenwick, yselivanov |
2017-04-18 23:45:45 | crenwick | set | messageid: <1492559145.11.0.288123202077.issue30098@psf.upfronthosting.co.za> |
2017-04-18 23:45:45 | crenwick | link | issue30098 messages |
2017-04-18 23:45:45 | crenwick | create | |
|