[issue37972] unittest.mock.call does not chain __getitem__ to another _Call object

Ben Hsing added the comment: Correction. I've now done this by delegating the resolution of attributes belonging to the tuple class to _Call.__getattr__ instead. Passed all build tests. -- ___ Python tracker <https://bugs.python.org/is

[issue37972] unittest.mock.call does not chain __getitem__ to another _Call object

Change by Ben Hsing : -- status: pending -> open ___ Python tracker <https://bugs.python.org/issue37972> ___ ___ Python-bugs-list mailing list Unsubscrib

[issue37972] unittest.mock.call does not chain __getitem__ to another _Call object

Ben Hsing added the comment: Agreed. I've submitted a new commit with the call chaining behavior now generalized for all dunder methods by delegating the resolution of all attributes not directly in the _Call object's __dict__ keys to the getattr method. -- status: open

[issue37972] unittest.mock.call does not chain __getitem__ to another _Call object

Change by Ben Hsing : -- keywords: +patch pull_requests: +15240 stage: -> patch review pull_request: https://github.com/python/cpython/pull/15565 ___ Python tracker <https://bugs.python.org/issu