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 txomon
Recipients brett.cannon, michael.foord, rbcollins, tsutsumi, txomon
Date 2016-12-20.00:22:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I found this while trying to test an async context manager. This is a critical feature to enable migrations to async code, as the impossibility to test something properly is not acceptable in many environments.

Implementing it in a way that __call__ returns an object capable of being coroutine or normal function would avoid having to implement Async specific Mocks, wouldn't it? I am not too confident, but would it be doable to have an implementation that depends on whether _is_coroutine is accessed or not?

I don't like it, but I really don't like the fact that we need to patch different all the methods depending on whether they are coroutine or not.

Obviously, having the __acall__ method would really help solving this issue.
Date User Action Args
2016-12-20 00:22:47txomonsetrecipients: + txomon, brett.cannon, rbcollins, michael.foord, tsutsumi
2016-12-20 00:22:47txomonsetmessageid: <>
2016-12-20 00:22:47txomonlinkissue26467 messages
2016-12-20 00:22:47txomoncreate