[issue8764] logging RotatingFileHandler cause too long to fininsh

Vinay Sajip added the comment: If you look closely, the system is not determining the name of the next log file. It is renaming log files - app.log.2 -> app.log.3, app.log.1 -> app.log.2, app.log -> app.log.1. The "next log file" is always app.log (or whatever the base file name is, I've just

[issue8764] logging RotatingFileHandler cause too long to fininsh

Changes by Antoine Pitrou : -- assignee: -> vinay.sajip nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue8764] logging RotatingFileHandler cause too long to fininsh

Changes by davy zhang : -- components: +Library (Lib) type: -> performance ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue8764] logging RotatingFileHandler cause too long to fininsh

New submission from davy zhang : the function below is used to determine the proper file name of the next log file. But the question is if I set a large number of self.backupCount like 1000, it will take too long to calculate the right file name. I think it could be a better way to do this