Author mark.dickinson
Recipients mark.dickinson, oneofthose
Date 2018-08-06.21:03:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1533589422.6.0.56676864532.issue34350@psf.upfronthosting.co.za>
In-reply-to
Content
The behaviour is long-standing and documented, in the note just under this entry: https://docs.python.org/3/library/logging.html?highlight=logging#logging.log

But I do agree that it's surprising and (at least for me) undesirable behaviour, in that it makes it way too easy to accidentally configure logging in library code, which is a no-no according to most logging "best practices" advice. (Applications do logging configuration; libraries should usually confine themselves to creating loggers and emitting log messages.)

But I suspect it would be rather hard to change now.
History
Date User Action Args
2018-08-06 21:03:42mark.dickinsonsetrecipients: + mark.dickinson, oneofthose
2018-08-06 21:03:42mark.dickinsonsetmessageid: <1533589422.6.0.56676864532.issue34350@psf.upfronthosting.co.za>
2018-08-06 21:03:42mark.dickinsonlinkissue34350 messages
2018-08-06 21:03:42mark.dickinsoncreate