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 mark.dickinson, oneofthose, vinay.sajip
Date 2018-08-08.22:14:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1533766459.81.0.56676864532.issue34350@psf.upfronthosting.co.za>
In-reply-to
Content
The logging module-level convenience functions are specifically there for the use of casual, short scripts where users don't want to be concerned with the details of loggers and handlers.

Even if you accidentally configure logging in library code because you typed logging.XXX() instead of logger.XXX(), that's just like any other bug introduced because of a typo. It would presumably get caught in testing.

Obviously, this behaviour can't be changed because of the need to maintain backward compatibility (and IMO there is no reason to change this behaviour, as it is like this by design).
History
Date User Action Args
2018-08-08 22:14:19vinay.sajipsetrecipients: + vinay.sajip, mark.dickinson, oneofthose
2018-08-08 22:14:19vinay.sajipsetmessageid: <1533766459.81.0.56676864532.issue34350@psf.upfronthosting.co.za>
2018-08-08 22:14:19vinay.sajiplinkissue34350 messages
2018-08-08 22:14:19vinay.sajipcreate