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 mitar, vinay.sajip
Date 2017-07-27.18:34:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1501180463.42.0.234023950812.issue30995@psf.upfronthosting.co.za>
In-reply-to
Content
> You only have to make sure they do not use this logger without knowing about new format, which can be done in various ways (like prefixing the name of the logger, for example).

That's the problem, right there. I don't think the ways of doing this are bulletproof and require too much cooperation between third-party libraries.

> using non-legacy formatting in logging message is really cumbersome

I don't see how it's "really cumbersome". A simple approach is outlined in

http://plumberjack.blogspot.co.uk/2010/10/supporting-alternative-formatting.html

So that logging using brace formatting could be as simple as 

logger.misc(__('User {} logged in', username))

which is also described in the documentation here:

https://docs.python.org/3.3/howto/logging-cookbook.html#use-of-alternative-formatting-styles
History
Date User Action Args
2017-07-27 18:34:23vinay.sajipsetrecipients: + vinay.sajip, mitar
2017-07-27 18:34:23vinay.sajipsetmessageid: <1501180463.42.0.234023950812.issue30995@psf.upfronthosting.co.za>
2017-07-27 18:34:23vinay.sajiplinkissue30995 messages
2017-07-27 18:34:23vinay.sajipcreate