[issue22494] default logging time string is not localized

2014-10-01 Thread Antoine Pitrou
Antoine Pitrou added the comment: I'm a bit surprised here, since the comma is not the default (US) decimal point. -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22494 ___

[issue22494] default logging time string is not localized

2014-10-01 Thread Georg Brandl
Georg Brandl added the comment: It's not so surprising, since the string before the milliseconds part is a strftime() result, not a whole number. The decimal point need not necessarily be used for this. Just like the rest of the default time format, it is probably best for the millisecond

[issue22494] default logging time string is not localized

2014-10-01 Thread Vinay Sajip
Vinay Sajip added the comment: ISO 8601 governs the format used. From the Wikipedia article on the same: A decimal mark, either a comma or a dot (without any preference as stated in resolution 10 of the 22nd General Conference CGPM in 2003, but with a preference for a comma according to ISO

[issue22494] default logging time string is not localized

2014-09-25 Thread Sean Dague
New submission from Sean Dague: The default time string is not localized for using locale specific formatting, but is instead hardcoded to a ','. https://hg.python.org/cpython/file/c87e00a6258d/Lib/logging/__init__.py#l483 demonstrates this. Instead I think we should set that to the value

[issue22494] default logging time string is not localized

2014-09-25 Thread Ned Deily
Changes by Ned Deily n...@acm.org: -- nosy: +vinay.sajip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22494 ___ ___ Python-bugs-list mailing list