Mark Blakeney added the comment:
Well my work-around is not ideal as I get an extra embedded space in those
messages. I'm surprised this is "not a common use case"? It doesn't really
worry me but it is a 3.6 incompatibility change which I would think is always
New submission from Mark Blakeney:
I have code which does a logging.addLevelName(logging.INFO, '') so that the
logging level name is not displayed in INFO messages, but is in all other
levels. I have been running this code fine since many versions of Python 2
through to 3.5.
Now ru
Changes by Mark Blakeney <[EMAIL PROTECTED]>:
--
nosy: +markb
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1641>
__
___
Python-bugs-list mailin
