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 vinay.sajip
Recipients steveha, vinay.sajip
Date 2018-05-15.07:40:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1526370043.91.0.682650639539.issue33506@psf.upfronthosting.co.za>
In-reply-to
Content
> Are you planning to remove the predefined filename templates

No. They work fine as is for most people, from what I can tell.

> it still has the limitation that when a logging file is active for writing log events, that file always has the same filename (self.baseFilename)

That's not a limitation particularly, it's that way by design.

> So if I needed to implement logging with a filename of: foo-YYYYmmdd.log at all times

Implement your own subclass and do whatever you need in there, including deletion of oldest files etc. Publish it on PyPI and see what the uptake is like. I'm not sure a donation of code in this area will be accepted, but there's no need for your bespoke handler subclass to be in the stdlib.
History
Date User Action Args
2018-05-15 07:40:43vinay.sajipsetrecipients: + vinay.sajip, steveha
2018-05-15 07:40:43vinay.sajipsetmessageid: <1526370043.91.0.682650639539.issue33506@psf.upfronthosting.co.za>
2018-05-15 07:40:43vinay.sajiplinkissue33506 messages
2018-05-15 07:40:43vinay.sajipcreate