kespindler added the comment:
Those new examples look good. I appreciate your revisiting the issue.
On Wed, Jan 15, 2014 at 7:12 AM, Vinay Sajip wrote:
>
> Vinay Sajip added the comment:
>
> Cookbook updated. See changesets 7c4f0c3dedaf and 0056aaf42bf7 for more
&
kespindler added the comment:
I definitely do recognize that important case. I think the proper solution,
however, to that is make a very clear warning in the documentation that
changing the style might affect the logging of 3rd party tools. Those users
would probably have to use the % style
kespindler added the comment:
I came across this issue while fixing issue20242. This issue (14031) still
exists and is a major source of annoyance and confusion, and I suggest
re-opening it.
Specifying the "{" style, while still being forced to use % formatting in log
statements i
kespindler added the comment:
I created a patch that fixes this behavior for both { and $ style formats.
Previously, default format strings were not being set correctly for those
styles. This patch ensures that the correct default_format string is used.
There is a minor "weirdness"
New submission from kespindler:
In Python 3.3, 3.4beta2, and bleeding edge (88411:e7d922d8ee03), the following
occurs
>>> import logging
>>> logging.basicConfig(style="{")
>>> logging.error("hello")
%(levelname)s:%(name)s:%(message)s
Of course,
