Vinay Sajip added the comment: I have now had some more time to think about this issue. I don't believe any changes are warranted, because "Errors should never pass silently. Unless explicitly silenced." and since rename errors are usually due to application- or environment-specific conditions, you need to handle these in application code.
If logging continues to use the existing log file because renaming fails, then it does not behave according to expectations - e.g. maximum sizes on log files will not be honoured. Likewise, logging does not attempt to use makedirs() to ensure that the parent directory path is created first - a typo in the path would lead to an unexpected location for the log file. While Python logging borrowed a lot from log4j, it is far from a straight port; the Zen of Python is different from the Zen of Java. ---------- resolution: -> invalid status: open -> closed _____________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1752539> _____________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
