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 skip.montanaro
Recipients pitrou, rhettinger, skip.montanaro, vinay.sajip, xiang.zhang
Date 2017-04-06.16:04:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CANc-5Uz+SOdWnR5on+=+t4Y8RNJTYPH0eMQkdBgi6kA2+10Hzg@mail.gmail.com>
In-reply-to <1491486566.36.0.503631152807.issue29955@psf.upfronthosting.co.za>
Content
Vinay> I would like to close this issue now...

Go for it.

As I indicated in a previous comment, the exercise was as much to try and
come to grips with the process as to actually make the change. There
certainly appear to be good reasons to leave well enough alone. My primary
(though minor) concerns at this point are:

* the datetime module hard-coded it one way (period) while the logging
package hard-coded it the other way.

* other logging packages I've used/inherited in other languages
(admittedly, pretty much Americo-centric) all seem to have used periods.

This only became an issue for me because I recently started using Flask,
which sets up the logging environment and provides no straightforward API
for me to reconfigure its logger. (Peter Otten demonstrated a way to do
this using functools.partial, which, while doable, certainly doesn't strike
me as straightforward.) In cases where I'm in complete control, configuring
my own logging environment makes sense. (In reality, when I'm in complete
control, I tend to roll my own 20-line Logger class and not use the logging
module at all, but that's a historical artifact of me discovering
performance issues several years ago in applications which logged heavily.
Those issues may well not exist today.)

Skip
History
Date User Action Args
2017-04-06 16:04:10skip.montanarosetrecipients: + skip.montanaro, rhettinger, vinay.sajip, pitrou, xiang.zhang
2017-04-06 16:04:10skip.montanarolinkissue29955 messages
2017-04-06 16:04:10skip.montanarocreate