Monty 0.0.19 supports open() and with blocks, but a file object is still not iterable. See pydantic/monty#490, which is still open. The instructions now state the limitation in three places and give the alternative next to each one: readlines() or read().split("\n"). Replace chr(10) with "\n" in the prose and in the example. Both work on 0.0.19, and chr(10) implies that the escape is broken. Add a test that pins the limitation. The test fails when Monty gains iteration support, which is the signal to relax the instructions. |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| conftest.py | ||
| test_models.py | ||
| test_sandbox.py | ||
| test_sandbox_multimodal.py | ||
| test_sandbox_toc.py | ||