Unitest.mock.MagicMock raises a StopIteration - not following PEP 479

It looks like Unitest.mock.MagicMock raises a StopIteration when repeated calls to the mock are made and an iterable is exhausted. After Python 3.7+, due to PEP 479, this raises a Runtime Error. This makes unit tests that worked in Python 3.6 fail, including any list comprehensions on MagicMock results. These can be easily caught with a try/except, but it's a bit clunky.

According to PEP 479 instead of StopIteration MagicMock should just return return when the iterable is exhausted. See here: https://peps.python.org/pep-0479/

Please let me know if I missed something on my end. Thanks for looking into this.

从 unittest.mock.MagicMock 开始，重现使用耗尽的 iterable 进行重复调用的情况，包括在列表推导式中的使用。结合 mock 的 iterable side effect 行为阅读 PEP 479；当耗尽的 iterable 的预期行为得到确立并由回归测试覆盖时，即视为完成。