Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
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']
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?
Well, we at least need some C level _fileio.
I don't see why we need some C level _fileio, the os module has everythign we need.
Patches welcome, of course!
Serhiy implemented the FileIO class in pure Python: see the issue bpo-21859 (patch under review).
pythongh-62184: Remove _pyio import of _io.FileIO
gh-62184: Remove _pyio import of _io.FileIO (gh-134192)
pythongh-62184: Remove _pyio import of _io.FileIO (pythongh-134192)
[3.13] gh-62184: Remove _pyio import of _io.FileIO (gh-134192) (gh-13…
[3.14] gh-62184: Remove _pyio import of _io.FileIO (gh-134192) (gh-13…
Triage: Can this be closed?
_pyio (Python implementation) still does an import io which unconditionally imports _io (C implementation) so I'd argue still not pep-399 compliant.
Activity
serhiy-storchaka commented on May 15, 2013
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?
benjaminp commented on May 15, 2013
Well, we at least need some C level _fileio.
alex commented on May 15, 2013
I don't see why we need some C level _fileio, the os module has everythign we need.
benjaminp commented on May 15, 2013
Patches welcome, of course!
vstinner commented on Jul 11, 2014
Serhiy implemented the FileIO class in pure Python: see the issue bpo-21859 (patch under review).
pythongh-62184: Remove _pyio import of _io.FileIO
gh-62184: Remove _pyio import of _io.FileIO (gh-134192)
pythongh-62184: Remove _pyio import of _io.FileIO (pythongh-134192)
pythongh-62184: Remove _pyio import of _io.FileIO (pythongh-134192)
[3.13] gh-62184: Remove _pyio import of _io.FileIO (gh-134192) (gh-13…
[3.14] gh-62184: Remove _pyio import of _io.FileIO (gh-134192) (gh-13…
pythongh-62184: Remove _pyio import of _io.FileIO (pythongh-134192)
pythongh-62184: Remove _pyio import of _io.FileIO (pythongh-134192)
pythongh-62184: Remove _pyio import of _io.FileIO (pythongh-134192)
StanFromIreland commented on Oct 31, 2025
Triage: Can this be closed?
cmaloney commented on Oct 31, 2025
_pyio (Python implementation) still does an import io which unconditionally imports _io (C implementation) so I'd argue still not pep-399 compliant.
pythongh-62184: Remove _pyio import of _io.FileIO (pythongh-134192)