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
<https://bugs.python.org/is
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
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,
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 -
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
