Skip Montanaro added the comment: 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 ---------- status: pending -> open _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29955> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
