Author eryksun
Recipients belopolsky, eryksun, mikekaganski, p-ganssle, paul.moore, steve.dower, tim.golden, zach.ware
Date 2021-06-11.11:10:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1623409839.91.0.903624715927.issue44352@roundup.psfhosted.org>
In-reply-to
Content
Note that this explanation in your commit is wrong and unhelpful: "likely because datetime.datetime.now in the native Windows Python takes into account both system timezone data and the TZ environment variable". When TZ is set, localtime() is based only on the TZ value, and daylight saving time uses only U.S. rules (e.g. beginning 2021-03-14 and ending 2021-11-07). The value must be of the form "tzn [+|-]hh[:mm[:ss] ][dzn]", but there is no validation. So "Europe/Moscow" is invalid and gets parsed as UTC with U.S. DST. I recommend clearing the TZ variable because the value format is non-standard, and its DST support is U.S.-centric nonsense.
History
Date User Action Args
2021-06-11 11:10:39eryksunsetrecipients: + eryksun, paul.moore, belopolsky, tim.golden, zach.ware, steve.dower, p-ganssle, mikekaganski
2021-06-11 11:10:39eryksunsetmessageid: <1623409839.91.0.903624715927.issue44352@roundup.psfhosted.org>
2021-06-11 11:10:39eryksunlinkissue44352 messages
2021-06-11 11:10:39eryksuncreate