[Python-Dev] Simplify the file-like-object interface (Replacement for print in Python 3.0)
Paul Moore
p.f.moore at gmail.com
Tue Sep 6 14:49:45 CEST 2005
More information about the Python-Dev mailing list
Tue Sep 6 14:49:45 CEST 2005
- Previous message: [Python-Dev] Simplify the file-like-object interface (Replacement for print in Python 3.0)
- Next message: [Python-Dev] Simplify the file-like-object interface
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 9/6/05, Fredrik Lundh <fredrik at pythonware.com> wrote: > Greg Ewing wrote: > > While we're on the subject, in Py3k I'd like to see > > readline(), readlines(), etc. removed from file objects > > and made builtin functions instead. It should only > > be necessary to implement read() and write() to get > > a file-like object having equal status with all > > others. > > maybe some variation of > > http://www.python.org/peps/pep-0246.html > > combined with "default adapters" could come in handy here ? That sounds like a good idea. I'm certainly getting concerned about the proliferation of methods that people "should" add to file-like objects, where read/write are the only fundamental ones needed. I can't see mixins working, as too many file-like objects are written in C... Paul.
- Previous message: [Python-Dev] Simplify the file-like-object interface (Replacement for print in Python 3.0)
- Next message: [Python-Dev] Simplify the file-like-object interface
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list