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 eryksun
Recipients GranPrego, eryksun, giampaolo.rodola, gregory.p.smith, paul.moore, steve.dower, tim.golden, zach.ware
Date 2018-05-22.18:57:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The 2nd example with creates two threads in the Python process, since you're redirecting both stdout and stderr to pipes and run() calls communicate(). The first example with subprocess.Popen() shouldn't create any threads. In either case, nothing in subprocess should be opening a handle for a thread.

Please attach a minimal script that reproduces the problem, preferably running a command everyone can test such as "python.exe -V" and preferably with shell=False if the problem can be reproduced without the shell. Also, describe your Python setup, i.e. the installed distribution and packages. Something could be monkey patching the subprocess module.
Date User Action Args
2018-05-22 18:57:01eryksunsetrecipients: + eryksun, gregory.p.smith, paul.moore, giampaolo.rodola, tim.golden, zach.ware, steve.dower, GranPrego
2018-05-22 18:57:01eryksunsetmessageid: <>
2018-05-22 18:57:01eryksunlinkissue33603 messages
2018-05-22 18:57:01eryksuncreate