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 に対する繰り返しの呼び出しを、list comprehension での使用も含めて再現します。PEP 479 を、mock の iterable な side effect の挙動と併せて読みます。使い果たされた iterable の意図した挙動が確立され、回帰テストでカバーされれば完了です。