[Python-ideas] Pythonic buffering in Py3 print()

[Guido van Rossum]

On Tue, Jan 10, 2012 at 5:27 AM, anatoly techtonik <techtonik at gmail.com>wrote:

> So, py3k print() is not pythonic. To make it pythonic, the output should
> be immediately available after you call it. If you need to buffer output -
> do this explicitly, because print() doesn't guarantee that it will be
> buffered anyway. If you care about performance - use sys.stdout directly
> and tune it explicitly.


That's utter bullshit.

However, I would be fine with adding a new keyword argument to print() in
3.3 to force a flush, as long as it defaults to off.

-- 
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20120110/96a7b240/attachment.html>