Message 131742 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	vstinner
Recipients	techtonik, vstinner
Date	2011-03-22.11:57:45
SpamBayes Score	0.00024218572
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
> How about making print() user-friendly with flushing after every call, > and if you want explicitly want speed - use buffered > sys.stdout.write/flush()? This is exactly the -u option of Python 2: use it if you would like a completly unbuffered sys.stdout in a portable way. In Python 3, it is only useful to flush at each line, even if the output is not a console, but a pipe (e.g. output redirected to a file). But nobody asked yet to have a fully unbuffered sys.stdout in Python 3.

> How about making print() user-friendly with flushing after every call,
> and if you want explicitly want speed - use buffered
> sys.stdout.write/flush()?

This is exactly the -u option of Python 2: use it if you would like a completly unbuffered sys.stdout in a portable way.

In Python 3, it is only useful to flush at each line, even if the output is not a console, but a pipe (e.g. output redirected to a file). But nobody asked yet to have a fully unbuffered sys.stdout in Python 3.

History
Date	User	Action	Args
2011-03-22 11:57:46	vstinner	set	recipients: + vstinner, techtonik
2011-03-22 11:57:46	vstinner	set	messageid: <[email protected]>
2011-03-22 11:57:45	vstinner	link	issue11633 messages
2011-03-22 11:57:45	vstinner	create