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 mschiess
Recipients mschiess, python-dev, vinay.sajip
Date 2022-01-14.15:11:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1642173100.77.0.134910514843.issue46377@roundup.psfhosted.org>
In-reply-to
Content
i've just checked PR and you're right, something with the PR went wrong.

Anyway, midnight (at least from the wording) specifies the "atTime". (which should be midnight). 


Again, if there's (by mistake) an interval bigger than 1 set(which in my mind makes no sense along to be used with midnight) things are getting pretty intransparent. The midnight handler created a logfile dated with 2021-12-15 (last night). Took me some time to get this sorted. (I've discovered, that I've set 30 in a default value file).

Agreed on the backward compatibility, but I would assume someone using "midnight" would not expect any other behavior than "daily at midnight" besides using the atTime to modify the rollover time. (my opinion)
History
Date User Action Args
2022-01-14 15:11:40mschiesssetrecipients: + mschiess, vinay.sajip, python-dev
2022-01-14 15:11:40mschiesssetmessageid: <1642173100.77.0.134910514843.issue46377@roundup.psfhosted.org>
2022-01-14 15:11:40mschiesslinkissue46377 messages
2022-01-14 15:11:40mschiesscreate