[issue39915] await_args_list in AsyncMock always refers to the last awaited call object

Karthikeyan Singaravelan added the comment: Thanks Mads Sejersen for the report. Closing this as fixed as it's merged to 3.9 and 3.8. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.9 ___ Python

[issue39915] await_args_list in AsyncMock always refers to the last awaited call object

Chris Withers added the comment: New changeset f6bdac1bf718eab0cc5b6554f363f21252d245ce by Miss Islington (bot) in branch '3.8': bpo-39915: Ensure await_args_list is updated according to the order in which coroutines were awaited (GH-18927)

[issue39915] await_args_list in AsyncMock always refers to the last awaited call object

Change by miss-islington : -- nosy: +miss-islington nosy_count: 8.0 -> 9.0 pull_requests: +18279 pull_request: https://github.com/python/cpython/pull/18927 ___ Python tracker

[issue39915] await_args_list in AsyncMock always refers to the last awaited call object

Chris Withers added the comment: New changeset e553f204bf0e39b1d701a364bc71b286acb9433f by Karthikeyan Singaravelan in branch 'master': bpo-39915: Ensure await_args_list is updated according to the order in which coroutines were awaited (GH-18924)

[issue39915] await_args_list in AsyncMock always refers to the last awaited call object

Change by Karthikeyan Singaravelan : -- keywords: +patch pull_requests: +18276 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18924 ___ Python tracker

[issue39915] await_args_list in AsyncMock always refers to the last awaited call object

Karthikeyan Singaravelan added the comment: Thanks for the report. At [0] self.call_args is used. This value is always the last call. So when the object is awaited it will be always the last call object and gets appended. The id of the call objects remain the same. The fix would be to