Test fails in daylight saving time TZs
See original GitHub issuetest_get_timezone_name():
> assert (dates.get_timezone_name(None, locale='en_US') ==
dates.get_timezone_name(datetime.now().replace(tzinfo=dates.LOCALTZ), locale='en_US'))
E assert 'Eastern European Summer Time' == 'Eastern Europ...Standard Time'
E - Eastern European Summer Time
E ? ^^^^
E + Eastern European Standard Time
E ? ^^^^^ +
I think this is a LOCALTZ bug (since LOCALTZ is janky at best), but can’t really be sure…
Note: should probably see if this is a regression introduced in 7800e547ed1710b24ee5679994cee6055c9c5698
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Failing tests because of the daylight saving time change
But after daylight saving time change, all my tests have failed because due to the change, the display text has changed to "10-10-2020...
Read more >Time parsing tests fail when localtime is in Daylight Savings
The seven asserts in the unit tests that depend on time parsing fail by being off by one hour, when localtime is in...
Read more >Default time tests fail in run-up to Daylight Saving clock change
This test failure was repeated in Friday 30th March test, which ran back at the usual time of around 00:15 GMT. Then on...
Read more >Impact of Daylight Saving Time on the Clinical Laboratory - PMC
Clinical laboratories should be aware that rare problems may occur due to issues with daylight saving time changes. Keywords: clinical chemistry tests, ...
Read more >Daylight saving time help and support - Windows Client
Describes the Microsoft policy in response to DST and time zone changes. ... for daylight saving time (DST) and time zone (TZ) information....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Oh, right, this was actually closed by #411.
Thanks for the additional data point, @BlackYoup. 😃