mock_open returns a mock object suitable for using as a mock file handle. File handles support iteration, so mock_open should support that. If possible it should be integrated with the current read/readlines support (only if possible), so the suggested patch may not be enough.


1.    Want to mock this:
with open(source_file, 'r') as f:             
    for line_num, line_text in enumerate(f):
        print line_text

2.  Tried this:
with patch('__builtin__.open', mock_open(read_data='text'), create=True) as p:

3.  enumerate causes a call to __iter__() which is not handled by the mock_open code.


What is the expected output? What do you see instead?

The __iter__ is allowed on the returned file handle

What version of the product are you using? On what operating system?

latest

Please provide any additional information below.

Patch would have mock_open setup handle.__iter__.return_value to a passed in parm or if none, possibly a iter(StringIO(read_data)) on the existing read_data parm to keep the interface unchanged.

I created a fix for this.  This also fixes a second issue in mock_open, which is that readline() raises StopIteration at EOF rather than returning empty strings.  See attached diff.
(Is there a  better procedure for submitting fixes?)

This is the corresponding patch to the test suite.

I noticed this issue too, thanks for fixing it!

Provided path did not work for me. Probably because lack of __next__ handler. I noticed that issue when interacting with cvs.reader and cvs.DictReader. After simple modification it seems to work fine.

For working around this issue on Python 3.5 it is sufficient to overwrite just the `return_value.__iter__` method of the object returned by `mock_open()` with an iterator that calls the mocked `readline()` method until it returns the empty string.

cf. e.g. https://github.com/gsauthof/utility/blob/6489c7215dac341be4e40e5348e64d69461766dd/user-installed.py#L176-L179

This also works in combination with `csv.reader()`, i.e. when calling it with the mocked file object.

The lack of dunder_iter support on mock_open has been resolved in Issue 32933 (Git Hub 5974).

Can I suggest that once the above PR is merged into 3.8 (due imminently allegedly <smile>), that we should then backport that fix into 3.5, 3.6 & 3.7 as a minimum ?

I am by no means an expert though.

Closing this as a duplicate of issue 32933. Let's discuss backporting to maintenance branches there.