[issue41449] An article on Python 3 stdout and stderr output buffering

Guido van Rossum added the comment: If you don't even know whether it's Python, Docker or Kubernetes you really need to ask somewhere else. Plenty of user groups around. Python detects tty using the standard UNIX isatty() function. To a tty we always get line buffering. To a file we use a

[issue41449] An article on Python 3 stdout and stderr output buffering

Anatoli Babenia added the comment: I didn't reopen the issue explicitly. Just pressed the submit button again when the notification about edited bug appeared. -- ___ Python tracker _

[issue41449] An article on Python 3 stdout and stderr output buffering

Anatoli Babenia added the comment: The point is that without a clear description of buffering in Python 3, it is impossible to understand what goes when Python is wrapped by Docker, supervisord, redirected to file etc. -- ___ Python tracker

[issue41449] An article on Python 3 stdout and stderr output buffering

Guido van Rossum added the comment: I don't know anything about Docker, so I can't help you there. Please don't reopen the issue again. -- resolution: -> wont fix status: open -> closed ___ Python tracker

[issue41449] An article on Python 3 stdout and stderr output buffering

Anatoli Babenia added the comment: To avoid too much outside reference, the commit message I am unsure of is this. > Run Python 3 in unbuffered mode to see lines in `docker logs` as soon as they > appear. When Python 3 is not attached to a terminal, it turns on the > buffering, like when `do

[issue41449] An article on Python 3 stdout and stderr output buffering

Guido van Rossum added the comment: I don't think that waiting another six months is going to make this happen either. Maybe you can petition realpython.com to publish something about this. Honestly it sounds like this ties too many different topics together to easily fit in the library docs

[issue41449] An article on Python 3 stdout and stderr output buffering

Anatoli Babenia added the comment: Not sure I can volunteer - need to find a sustenance ASAP. But given that nothing moved in this direction over the past 6 months, another week spent not writing this stuff won't change anything. In any case it would start with the following problem - "Logs

[issue41449] An article on Python 3 stdout and stderr output buffering

Guido van Rossum added the comment: Maybe you’ll get some explanation or pointers on python-list. Or were you volunteering to write something? -- nosy: +gvanrossum ___ Python tracker

[issue41449] An article on Python 3 stdout and stderr output buffering

Change by tedder : -- nosy: +tedder ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/m

[issue41449] An article on Python 3 stdout and stderr output buffering

New submission from Anatoli Babenia : 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 Ku