Home Original page

bpo-13601: always use line-buffering for sys.stderr by jendrikseipp · Pull Request #17646 · python/cpython

@jendrikseipp

@jendrikseipp

vstinner

vstinner

vstinner

vstinner

vstinner

@jendrikseipp

serhiy-storchaka

@jendrikseipp

vstinner

@pitrou

shihai1991 pushed a commit to shihai1991/cpython that referenced this pull request

Jan 31, 2020

@jendrikseipp @shihai1991

hauntsaninja pushed a commit to hauntsaninja/mypy that referenced this pull request

May 8, 2020 
There's a fun Python 3.9 only test case failure, where "Daemon started" is
output after the error message from parsing options.  I ended up needing to
bisect to figure out why this breaks consistently on Python 3.9. The issue is
caused by python/cpython#17646 (which fixes a
surprisingly old issue). I'm biased because I just spent some time figuring this
out, but maybe it should be mentioned in the What's New.

hauntsaninja pushed a commit to hauntsaninja/mypy that referenced this pull request

May 8, 2020 
There's a fun Python 3.9 only test case failure, where "Daemon started" is
output after the error message from parsing options.  I ended up needing to
bisect to figure out why this consistently breaks on Python 3.9. The issue is
caused by python/cpython#17646 (which fixes a
surprisingly old BPO).

msullivan pushed a commit to python/mypy that referenced this pull request

May 20, 2020 
There's a fun Python 3.9 only test case failure, where "Daemon started" is
output after the error message from parsing options.  I ended up needing to
bisect to figure out why this consistently breaks on Python 3.9. The issue is
caused by python/cpython#17646 (which fixes a
surprisingly old BPO).

Co-authored-by: hauntsaninja <>