[issue20124] The documentation for the atTime parameter of TimedRotatimeFileHandler is confusing
New submission from R. David Murray: The docs say that you can specify 'atTime' with a 'when' of 'midnight', but that makes no sense on the face of it. atTime with a weekday specification makes sense, but it would also make sense to use atTime with a when of D (and an interval), which is not mentioned as a possibility. It could also make sense to use it with other intervals (in other words, use the atTime as the starting point for the rotation calculation, instead of the last mod time or 'now'). If that doesn't work it should be stated that atTime will be ignored in those cases. Probably all the time related entries should be rewritten with the existence of atTime in mind, in order to clarify all the possible (and not possible) interactions. ---------- assignee: docs@python components: Documentation messages: 207323 nosy: docs@python, r.david.murray, vinay.sajip priority: normal severity: normal stage: needs patch status: open title: The documentation for the atTime parameter of TimedRotatimeFileHandler is confusing versions: Python 3.4 _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue20124> _______________________________________
Roundup Robot added the comment: New changeset 8d13c1f33d21 by Vinay Sajip in branch 'default': Closes #20124: clarified usage of the atTime parameter in TimedRotatingFileHandler documentation. https://hg.python.org/cpython/rev/8d13c1f33d21 ---------- nosy: +python-dev resolution: -> fixed stage: needs patch -> resolved status: open -> closed _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue20124> _______________________________________
participants (2)
-
R. David Murray
-
Roundup Robot