Repository navigation
io and _pyio modules require the _io module #62184
Copy link
Copy link
Open
Labels
stdlibStandard Library Python modules in the Lib/ directoryStandard Library Python modules in the Lib/ directorytopic-IOtype-featureA feature request or enhancementA feature request or enhancement
Description
Activity
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?
- addedtype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
on May 15, 2013 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!
- addedtype-featureA feature request or enhancementA feature request or enhancementand removedtype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
on May 18, 2013 Serhiy implemented the FileIO class in pure Python: see the issue bpo-21859 (patch under review).
- added a commit that references this issue
on May 18, 2025 - addedstdlibStandard Library Python modules in the Lib/ directoryStandard Library Python modules in the Lib/ directory
on May 18, 2025 - added a commit that references this issue
on May 21, 2025 Triage: Can this be closed?
_pyio(Python implementation) still does animport iowhich unconditionally imports_io(C implementation) so I'd argue still not pep-399 compliant.
Metadata
Metadata
Assignees
Labels
stdlibStandard Library Python modules in the Lib/ directoryStandard Library Python modules in the Lib/ directorytopic-IOtype-featureA feature request or enhancementA feature request or enhancement
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:
bugs.python.org fields:
Linked PRs