Message267479
Taking a look at the code, this may require a bit more discussion.
Mock's classes create copies of themselves when an attribute is accessed. As such, I can't just add __aexit__ and have it generate a different mock type entirely, unless I know exactly what an async variant of this mock is.
If there was a way to specifically provide a function for asynchronous situations, like __acall__, that would make this a lot easier as well.
Anyway, my proposal now is:
create new classes MockAsync and MagicMockAsync, and have MockAsync and MagicMockAsync implement the __aexit__ and __aenter__ methods.
How is that as an approach? |
|
Date |
User |
Action |
Args |
2016-06-05 21:51:27 | tsutsumi | set | recipients:
+ tsutsumi, brett.cannon, michael.foord |
2016-06-05 21:51:27 | tsutsumi | set | messageid: <1465163487.53.0.546088978024.issue26467@psf.upfronthosting.co.za> |
2016-06-05 21:51:27 | tsutsumi | link | issue26467 messages |
2016-06-05 21:51:27 | tsutsumi | create | |
|