STINNER Victor <vstinner@python.org> added the comment:
Calling proc.communicate() after proc.stdout.read() doesn't seem to be supported. What is your use case? Why not just calling communicate()? Why not only using stdout directly?
----------
components: -2to3 (2.x to 3.x conversion tool), IO
nosy: +gregory.p.smith
title: BufferedReader causes Popen.communicate losing the remaining output. -> subprocess: Calling Popen.communicate() after Popen.stdout.read() returns an empty string
versions: -Python 3.6, Python 3.7, Python 3.8, Python 3.9
_______________________________________
Python tracker <report@bugs.python.org>
<https://bugs.python.org/issue41406>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com
Calling proc.communicate() after proc.stdout.read() doesn't seem to be supported. What is your use case? Why not just calling communicate()? Why not only using stdout directly?
----------
components: -2to3 (2.x to 3.x conversion tool), IO
nosy: +gregory.p.smith
title: BufferedReader causes Popen.communicate losing the remaining output. -> subprocess: Calling Popen.communicate() after Popen.stdout.read() returns an empty string
versions: -Python 3.6, Python 3.7, Python 3.8, Python 3.9
_______________________________________
Python tracker <report@bugs.python.org>
<https://bugs.python.org/issue41406>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com