Author mark.dickinson
Recipients eamanu, mark.dickinson, porton, steven.daprano, vinay.sajip, xtreak
Date 2018-12-19.10:37:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1545215842.65.0.788709270274.issue35530@psf.upfronthosting.co.za>
In-reply-to
Content
The call to `logging.error` is *not* irrelevant here. It's causing an implicit, and surprising (albeit documented), call to `logging.basicConfig`.

https://bugs.python.org/issue34350 is essentially the same issue. That issue was closed as "not a bug", though I think a more appropriate resolution would have been "won't fix". In my mind, this is a design flaw in logging, and it's one that's caused my colleagues and me real-world pain on multiple occasions.

There may be backwards compatibility constraints that make it impossible to fix this. I haven't looked into what would be needed.
History
Date User Action Args
2018-12-19 10:37:22mark.dickinsonsetrecipients: + mark.dickinson, vinay.sajip, steven.daprano, porton, eamanu, xtreak
2018-12-19 10:37:22mark.dickinsonsetmessageid: <1545215842.65.0.788709270274.issue35530@psf.upfronthosting.co.za>
2018-12-19 10:37:22mark.dickinsonlinkissue35530 messages
2018-12-19 10:37:22mark.dickinsoncreate