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 serhiy.storchaka, vinay.sajip
Date 2015-01-02.16:46:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1420217166.6.0.633227797492.issue23151@psf.upfronthosting.co.za>
In-reply-to
Content
The code in Manager.getLogger() allows an overriding logger class for that manager instance only - if it's not set (which is the default), it uses the module global _loggerClass. The lines

rv = (self.loggerClass or _loggerClass)(name)

indicate this.

The module global _loggerClass is initialized to None initially, simply so that it can be defined before being used in Manager (so really, for readability). Later, after Logger is defined, _loggerClass is set to Logger.

Is this causing some actual problem?
History
Date User Action Args
2015-01-02 16:46:06vinay.sajipsetrecipients: + vinay.sajip, serhiy.storchaka
2015-01-02 16:46:06vinay.sajipsetmessageid: <1420217166.6.0.633227797492.issue23151@psf.upfronthosting.co.za>
2015-01-02 16:46:06vinay.sajiplinkissue23151 messages
2015-01-02 16:46:05vinay.sajipcreate