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 vinay.sajip
Recipients Claudiu.Popa, Shiming He, andreasvc, bquinlan, dan.oreilly, giampaolo.rodola, jcon, josh.r, mark.dickinson, mdengler, nchammas, pitrou, s0undt3ch, serhiy.storchaka, thehesiod, vinay.sajip
Date 2017-11-09.10:25:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1510223113.74.0.213398074469.issue21423@psf.upfronthosting.co.za>
In-reply-to
Content
> What is the best way to silence logging in subprocesses?

Are you referring to the output shown in msg305601? If it's caused by logging statements, the best way would be either to pipe stderr to /dev/null or to change the logging to use sys.stdout (sys.stderr is just the default) and then pipe stdout to /dev/null.

I hope I haven't misunderstood your question, but I fear I may have.
History
Date User Action Args
2017-11-09 10:25:13vinay.sajipsetrecipients: + vinay.sajip, bquinlan, mark.dickinson, pitrou, giampaolo.rodola, Claudiu.Popa, jcon, serhiy.storchaka, mdengler, s0undt3ch, thehesiod, josh.r, andreasvc, dan.oreilly, nchammas, Shiming He
2017-11-09 10:25:13vinay.sajipsetmessageid: <1510223113.74.0.213398074469.issue21423@psf.upfronthosting.co.za>
2017-11-09 10:25:13vinay.sajiplinkissue21423 messages
2017-11-09 10:25:13vinay.sajipcreate