Skip to content

io and _pyio modules require the _io module #62184

Description

@serhiy-storchaka
BPO 17984
Nosy @pitrou, @vstinner, @benjaminp, @alex, @hynek, @serhiy-storchaka

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2013-05-15.19:49:27.725>
labels = ['type-feature', 'expert-IO']
title = 'io and _pyio modules require the _io module'
updated_at = <Date 2014-07-11.14:40:31.288>
user = 'https://github.com/serhiy-storchaka'

bugs.python.org fields:

activity = <Date 2014-07-11.14:40:31.288>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IO']
creation = <Date 2013-05-15.19:49:27.725>
creator = 'serhiy.storchaka'
dependencies = []
files = []
hgrepos = []
issue_num = 17984
keywords = []
message_count = 5.0
messages = ['189295', '189296', '189297', '189298', '222752']
nosy_count = 8.0
nosy_names = ['pitrou', 'vstinner', 'benjamin.peterson', 'stutzbach', 'alex', 'hynek', 'piotr.dobrogost', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue17984'
versions = ['Python 3.4']

Linked PRs

Activity

  1. serhiy-storchaka commented on May 15, 2013

    @serhiy-storchaka
    MemberAuthor

    io and _pyio modules don't usable without the _io module. In particular when 2.7 build without unicode. Why we have a Python implementation if it can't be used as a fallback when a C implementation is not available?

  2. benjaminp commented on May 15, 2013

    @benjaminp
    Contributor

    Well, we at least need some C level _fileio.

  3. alex commented on May 15, 2013

    @alex
    Member

    I don't see why we need some C level _fileio, the os module has everythign we need.

  4. benjaminp commented on May 15, 2013

    @benjaminp
    Contributor

    Patches welcome, of course!

  5. added
    type-featureA feature request or enhancement
    and removed
    type-bugAn unexpected behavior, bug, or error
    on May 18, 2013
  6. vstinner commented on Jul 11, 2014

    @vstinner
    Member

    Serhiy implemented the FileIO class in pure Python: see the issue bpo-21859 (patch under review).

  7. transferred this issue fromon Apr 10, 2022
  8. added a commit that references this issue on May 18, 2025
  9. added
    stdlibStandard Library Python modules in the Lib/ directory
    on May 18, 2025
  10. added a commit that references this issue on May 21, 2025
  11. added 2 commits that reference this issue on May 21, 2025
  12. added 2 commits that reference this issue on May 21, 2025
  13. added a commit that references this issue on May 26, 2025
  14. added a commit that references this issue on Jul 12, 2025
  15. added a commit that references this issue on Aug 4, 2025
  16. StanFromIreland commented on Oct 31, 2025

    @StanFromIreland
    Member

    Triage: Can this be closed?

  17. cmaloney commented on Oct 31, 2025

    @cmaloney
    Contributor

    _pyio (Python implementation) still does an import io which unconditionally imports _io (C implementation) so I'd argue still not pep-399 compliant.

  18. added a commit that references 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

    stdlibStandard Library Python modules in the Lib/ directorytopic-IOtype-featureA feature request or enhancement

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions