Skip to content

Use implemenation-specific I/O open / constructors in tests #133982

Description

@cmaloney

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 the self. 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

Activity

  1. added a commit that references this issue on May 13, 2025
  2. added 2 commits that reference this issue on May 18, 2025
  3. added a commit that references this issue on May 21, 2025
  4. added 2 commits that reference this issue on May 21, 2025
  5. added a commit that references this issue on May 21, 2025
  6. added 2 commits that reference this issue on May 21, 2025
  7. added 3 commits that reference this issue on May 21, 2025
  8. 18 remaining items

  9. added a commit that references this issue on Jul 12, 2025
  10. added 2 commits that reference this issue on Jul 13, 2025
  11. added 4 commits that reference this issue on Aug 4, 2025
  12. added 2 commits that reference this issue on Aug 19, 2025
  13. added 2 commits that reference this issue on Sep 2, 2025
  14. cmaloney commented on Nov 7, 2025

    @cmaloney
    ContributorAuthor

    Closing, I think these are all fixed. test_largefile the one instance is in TestSocketSendfile which is _io only.

  15. added 2 commits that reference this issue on Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    testsTests in the Lib/test dirtopic-IOtype-bugAn unexpected behavior, bug, or error

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions