Repository navigation
Use implemenation-specific I/O open / constructors in tests #133982
Copy link
Copy link
Closed
Labels
testsTests in the Lib/test dirTests in the Lib/test dirtopic-IOtype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Description
Activity
- addedtype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
on May 13, 2025 - added a commit that references this issue
on May 13, 2025 18 remaining items
- added 4 commits that reference this issue
on Aug 4, 2025 Closing, I think these are all fixed.
test_largefilethe one instance is inTestSocketSendfilewhich is_ioonly.
Metadata
Metadata
Assignees
Labels
testsTests in the Lib/test dirTests in the Lib/test dirtopic-IOtype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Bug report
Bug description:
Most I/O tests are setup for running on multiple implementations. As tests have been added for bug fixes some now use
open()or the class constructor directly instead of theself.version which does implementation delegation. This means that some features are not tested when the I/O module implementation is changed (ex._io,_pyio).I'm planning to use this as a meta issue as I find individual cases and update the test, fixing up implementations as needed to get tests passing.
CPython versions tested on:
CPython main branch
Operating systems tested on:
No response
Linked PRs
openintest_fileio.OtherFileTests(GH-135364) #136148openintest_fileio.OtherFileTests(GH-135364) #136149