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 p-ganssle
Recipients belopolsky, p-ganssle, tim.peters
Date 2016-11-03.19:26:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Of the `tzinfo` implementations provided by `python-dateutil`, `tzrange`, `tzstr` (GNU TZ strings), `tzwin` (Windows style time zones) and `tzlocal` all satisfy this condition. These are basically all implementations of default system time zone information.

With current implementations `tzfile` and `tzical` also use the invariant algorithm, though theoretically there are edge cases where this will cause problems, and those should have their `fromutc()` adjusted.

In any case, I can't think of a single actual downside to this change - all it does is preserve the original behavior of `fromutc()`. As currently implemented, the algorithm is simply wrong when `dst()` is affected by `fold`, and this change would have no effect on zones where `dst()` is *not* affected by fold.
Date User Action Args
2016-11-03 19:26:01p-gansslesetrecipients: + p-ganssle, tim.peters, belopolsky
2016-11-03 19:26:01p-gansslesetmessageid: <>
2016-11-03 19:26:01p-gansslelinkissue28602 messages
2016-11-03 19:26:01p-gansslecreate