[issue9838] Inadequate C-API to Python 3 I/O objects

2013-07-08 Thread Christian Heimes
Christian Heimes added the comment: I agree with Antoine. If you are still interested to improve the situation then please start a discussion on the python-ideas mailing list. -- nosy: +christian.heimes resolution: - postponed status: open - closed

[issue9838] Inadequate C-API to Python 3 I/O objects

2010-09-12 Thread Pauli Virtanen
New submission from Pauli Virtanen p...@iki.fi: The C-API exposed by the `io` module on Python 3.1/3.2 is very limited, and makes interfacing with Python file objects in extension modules difficult. In more detail: 1) Because the Python layer has buffering etc., the file handle returned by

[issue9838] Inadequate C-API to Python 3 I/O objects

2010-09-12 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: Instead, every call must go through PyObject_CallMethod, and the file objects only handle `PyBytes` and `PyByteArray` which are cumbersome and inefficient to use in extension modules. Because of the generic nature of the 3.x I/O stack, even

[issue9838] Inadequate C-API to Python 3 I/O objects

2010-09-12 Thread Éric Araujo
Changes by Éric Araujo mer...@netwok.org: -- versions: -Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9838 ___ ___ Python-bugs-list