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 serhiy.storchaka
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:56:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1510224996.51.0.213398074469.issue21423@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not well experienced with logging, but if we can change the logging in subprocesses, I think we could change it to not output messages at all. It would be better to save logging messages in subprocesses and check that expected logging messages are emitted in the main process. There is assertLogs(), but it works only with logging in the same process.
History
Date User Action Args
2017-11-09 10:56:36serhiy.storchakasetrecipients: + serhiy.storchaka, vinay.sajip, bquinlan, mark.dickinson, pitrou, giampaolo.rodola, Claudiu.Popa, jcon, mdengler, s0undt3ch, thehesiod, josh.r, andreasvc, dan.oreilly, nchammas, Shiming He
2017-11-09 10:56:36serhiy.storchakasetmessageid: <1510224996.51.0.213398074469.issue21423@psf.upfronthosting.co.za>
2017-11-09 10:56:36serhiy.storchakalinkissue21423 messages
2017-11-09 10:56:36serhiy.storchakacreate