Author Anatoli Babenia
Recipients Anatoli Babenia, docs@python
Date 2020-07-31.10:10:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1596190232.56.0.383059757324.issue41449@roundup.psfhosted.org>
In-reply-to
Content
It is hard to find info why Python 3 buffers stdout/stderr. The buffering causes problems when debugging Python apps in Docker and Kubernetes, and it is unclear if it is Python 3 who starts to buffer stdout if no tty is attached, it is Docker, or it is Kubernetes.

The only bit of info that could be searched is the description of -u option https://docs.python.org/3.8/using/cmdline.html?#cmdoption-u which is not linked to any article.

The `-u` description also says.

> Changed in version 3.7: The text layer of the stdout and stderr streams now is unbuffered.

However, I don't understand what is the text layers of stdout. And there is no description of behaviour when the output is not attached, and when the output is redirected.
History
Date User Action Args
2020-07-31 10:10:32Anatoli Babeniasetrecipients: + Anatoli Babenia, docs@python
2020-07-31 10:10:32Anatoli Babeniasetmessageid: <1596190232.56.0.383059757324.issue41449@roundup.psfhosted.org>
2020-07-31 10:10:32Anatoli Babenialinkissue41449 messages
2020-07-31 10:10:31Anatoli Babeniacreate