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 vstinner
Recipients gvanrossum, luhn, vstinner, yselivanov
Date 2015-11-10.21:53:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1447192425.94.0.68798086103.issue25599@psf.upfronthosting.co.za>
In-reply-to
Content
>>> asyncio.iscoroutinefunction(unittest.mock.Mock())
<Mock name='mock._is_coroutine' id='4544068072'>

Yeah, I already had this issue when I wrote unit tests using mock :-/ I didn't find an obvious fix for this issue, and it's quite easy to workaround it.

It looks like the "m._is_coroutine = False" is not used in asyncio tests. I don't recall how I worked around the issue in asyncio tests...
History
Date User Action Args
2015-11-10 21:53:45vstinnersetrecipients: + vstinner, gvanrossum, yselivanov, luhn
2015-11-10 21:53:45vstinnersetmessageid: <1447192425.94.0.68798086103.issue25599@psf.upfronthosting.co.za>
2015-11-10 21:53:45vstinnerlinkissue25599 messages
2015-11-10 21:53:45vstinnercreate