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 r.david.murray
Recipients crenwick, r.david.murray, yselivanov
Date 2017-04-19.02:22:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1492568523.54.0.370028434129.issue30098@psf.upfronthosting.co.za>
In-reply-to
Content
I don't think your specialized error message adds anything.  The the most common mistake, IMO, is going to be not realizing that run_coroutine_threadsafe don't return one of the acceptable types.  So being told that concurrent.future.Future is not acceptable will add zero additional information.  I think the only change that needs to be made is to make the existing message say 'asyncio.Future' instead of just 'Future'.
History
Date User Action Args
2017-04-19 02:22:03r.david.murraysetrecipients: + r.david.murray, yselivanov, crenwick
2017-04-19 02:22:03r.david.murraysetmessageid: <1492568523.54.0.370028434129.issue30098@psf.upfronthosting.co.za>
2017-04-19 02:22:03r.david.murraylinkissue30098 messages
2017-04-19 02:22:02r.david.murraycreate