[New-bugs-announce] [issue38122] AsyncMock force always creating an AsyncMock for child mocks

[Lisa Roach]

New submission from Lisa Roach <lisaroach14 at gmail.com>:

This idea has been brought up in person before and also discussed on AsyncTest: https://github.com/Martiusweb/asynctest/issues/100


It could be useful if someone has a lot of attributes that are also async that need to be mocked. 

It could probably be done with a flag that gets passed on to _get_child_mock and overrides the if statement to always return an AsyncMock.


Looking mostly for if people think this is a good idea/bad idea and help see around any corners that may be there.

----------
assignee: lisroach
components: Library (Lib)
messages: 351991
nosy: cjw296, ezio.melotti, lisroach, michael.foord, xtreak
priority: low
severity: normal
status: open
title: AsyncMock force always creating an AsyncMock for child mocks
type: behavior

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38122>
_______________________________________