A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2005-September/056222.html below:

[Python-Dev] Simplify the file-like-object interface (Replacement for print in Python 3.0)

[Python-Dev] Simplify the file-like-object interface (Replacement for print in Python 3.0) [Python-Dev] Simplify the file-like-object interface (Replacement for print in Python 3.0)Fredrik Lundh fredrik at pythonware.com
Tue Sep 6 14:03:01 CEST 2005
Greg Ewing wrote:

>> (you completely missed the point -- today's print mechanism works on *any* object
>> that implements a "write" method, no just file objects.  saying that "oh, all you need is
>> to add a method" or "here's a nice mixin" doesn't give you a print replacement)
>
> 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 ?

</F> 



More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4