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 sdwarwick
Recipients mitar, sdwarwick, vinay.sajip
Date 2017-09-24.17:34:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1506274467.53.0.663463739827.issue30995@psf.upfronthosting.co.za>
In-reply-to
Content
you probably have already considered this, but I just wanted to ask if it might be worth considering turning the problem "upside down" to make things easier.

  I'm interpreting the problem that there are variables we'd like to add to the output log that are provided inside the logger, which is why we need to use a specific type of format string to make sure you add them correctly.   If instead, these same variables are simply exposed as logger attributes, we could just create the complete formatted string when we call the logger.  

logger.info( " {:s} {:s} ", logger.name, logger.module ) 

does this make any sense?
History
Date User Action Args
2017-09-24 17:34:27sdwarwicksetrecipients: + sdwarwick, vinay.sajip, mitar
2017-09-24 17:34:27sdwarwicksetmessageid: <1506274467.53.0.663463739827.issue30995@psf.upfronthosting.co.za>
2017-09-24 17:34:27sdwarwicklinkissue30995 messages
2017-09-24 17:34:27sdwarwickcreate