➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients Frost Ming, gregory.p.smith, gstarck, vstinner
Date 2020-08-03.23:30:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1596497407.35.0.0157317903913.issue41406@roundup.psfhosted.org>
In-reply-to
Content 
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?
History
Date User Action Args
2020-08-03 23:30:07vstinnersetrecipients: + vstinner, gregory.p.smith, gstarck, Frost Ming
2020-08-03 23:30:07vstinnersetmessageid: <1596497407.35.0.0157317903913.issue41406@roundup.psfhosted.org>
2020-08-03 23:30:07vstinnerlinkissue41406 messages
2020-08-03 23:30:07vstinnercreate