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 r.david.murray
Recipients docs@python, r.david.murray, vinay.sajip
Date 2014-01-04.23:48:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1388879336.03.0.25076651665.issue20124@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2014-01-04 23:48:56r.david.murraysetrecipients: + r.david.murray, vinay.sajip, docs@python
2014-01-04 23:48:56r.david.murraysetmessageid: <1388879336.03.0.25076651665.issue20124@psf.upfronthosting.co.za>
2014-01-04 23:48:55r.david.murraylinkissue20124 messages
2014-01-04 23:48:55r.david.murraycreate