PythonExtra/tests/io/file_readinto.py

b = bytearray(30)
f = open("data/file1", "rb")
print(f.readinto(b))
print(b)
f = open("data/file2", "rb")
print(f.readinto(b))
print(b)

# readinto() on writable file
f = open("data/file1", "ab")
try:
    f.readinto(bytearray(4))
except OSError:
    print("OSError")
unix, stmhal: Implement file.readinto() method. Also, usocket.readinto(). Known issue is that .readinto() should be available only for binary files, but micropython uses single method table for both binary and text files. 2014-10-18 21:44:07 +02:00			`b = bytearray(30)`
tests/run-tests.py: Ensure correct cwd for mpy tests. Previously when using --via-mpy, the file was compiled to tests/<tmp>.mpy and then run using `micropython -m <tmp>` in the current cwd (usually tests/). This meant that an import in the test would be resolved relative to tests/. This is different to regular (non-via-mpy) tests, where we run (for example) `micropython basics/test.py` which means that an import would be resolved relative to basics/. Now --via-mpy matches the .py behavior. This is important because: a) It makes it so import tests do the right thing. b) There are directory names in tests/ that match built-in module names. Furthermore, it always ensures the cwd (for both micropython and cpython) is the test directory (e.g. basics/) rather than being left unset. This also makes it clearer inside the test that e.g. file access is relative to the Python file. Updated tests with file paths to match. This work was funded through GitHub Sponsors. Signed-off-by: Jim Mussared <jim.mussared@gmail.com> 2023-05-11 06:28:35 +02:00			`f = open("data/file1", "rb")`
unix, stmhal: Implement file.readinto() method. Also, usocket.readinto(). Known issue is that .readinto() should be available only for binary files, but micropython uses single method table for both binary and text files. 2014-10-18 21:44:07 +02:00			`print(f.readinto(b))`
			`print(b)`
tests/run-tests.py: Ensure correct cwd for mpy tests. Previously when using --via-mpy, the file was compiled to tests/<tmp>.mpy and then run using `micropython -m <tmp>` in the current cwd (usually tests/). This meant that an import in the test would be resolved relative to tests/. This is different to regular (non-via-mpy) tests, where we run (for example) `micropython basics/test.py` which means that an import would be resolved relative to basics/. Now --via-mpy matches the .py behavior. This is important because: a) It makes it so import tests do the right thing. b) There are directory names in tests/ that match built-in module names. Furthermore, it always ensures the cwd (for both micropython and cpython) is the test directory (e.g. basics/) rather than being left unset. This also makes it clearer inside the test that e.g. file access is relative to the Python file. Updated tests with file paths to match. This work was funded through GitHub Sponsors. Signed-off-by: Jim Mussared <jim.mussared@gmail.com> 2023-05-11 06:28:35 +02:00			`f = open("data/file2", "rb")`
unix, stmhal: Implement file.readinto() method. Also, usocket.readinto(). Known issue is that .readinto() should be available only for binary files, but micropython uses single method table for both binary and text files. 2014-10-18 21:44:07 +02:00			`print(f.readinto(b))`
			`print(b)`
tests: Add tests for stream IO errors. 2015-12-23 23:37:02 +01:00
			`# readinto() on writable file`
tests/run-tests.py: Ensure correct cwd for mpy tests. Previously when using --via-mpy, the file was compiled to tests/<tmp>.mpy and then run using `micropython -m <tmp>` in the current cwd (usually tests/). This meant that an import in the test would be resolved relative to tests/. This is different to regular (non-via-mpy) tests, where we run (for example) `micropython basics/test.py` which means that an import would be resolved relative to basics/. Now --via-mpy matches the .py behavior. This is important because: a) It makes it so import tests do the right thing. b) There are directory names in tests/ that match built-in module names. Furthermore, it always ensures the cwd (for both micropython and cpython) is the test directory (e.g. basics/) rather than being left unset. This also makes it clearer inside the test that e.g. file access is relative to the Python file. Updated tests with file paths to match. This work was funded through GitHub Sponsors. Signed-off-by: Jim Mussared <jim.mussared@gmail.com> 2023-05-11 06:28:35 +02:00			`f = open("data/file1", "ab")`
tests: Add tests for stream IO errors. 2015-12-23 23:37:02 +01:00			`try:`
			`f.readinto(bytearray(4))`
			`except OSError:`
			`print("OSError")`