Win10 with turned off dst always run into offset error
See original GitHub issueI am using APScheduler and this uses tzlocal. My flask server runs on a Windows10-PC with turned off day saving time options (means no extra offset in summer here in germany). But this results in errors in:
from tzlocal import get_localzone
tz = get_localzone()
How do I solve this issue?
Best regards Sören
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Fix Windows 10 time sync offset - Tutorial - Dedoimedo
Tutorial explaining how to fix time offset in Windows 10, including overview of the problem, local time versus UTC, hardware clock, ...
Read more >[Pinned] ValueError: Timezone offset does not match system ...
The problem is that by enabling automatic daylight saving time, windows adds 1 more WRONG hour. I can't keep a wrong clock on...
Read more >Windows starts and ends daylight saving time incorrectly if the ...
Discusses a problem that occurs when the time zone is set incorrectly and the "Automatically adjust clock for daylight saving changes" check box...
Read more >Windows 10 always showing wrong time (when dual-booting ...
Press Windows key + R · Type services.msc. · Double Click "Windows Time" in the Name column. · Change "Startup type" to "Automatic"...
Read more >Windows time zone wrong/not saving when settings are ...
Time Zone Settings dialog box. Instead, we suggest that you select a time zone that does not observe daylight saving time and that...
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 FreeTop 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
Top GitHub Comments
Hmm, I have to think about if that’s possible.
This restrictions comes from the galvanic steering server that also runs on that server that doesn’t want to handle time holes 😃 but nevertheless my flask server usually uses timezones in a correct way. But in this case the APScheduler uses your package inside, but I figured out that I can configure UTC timezone for that package. Thus that should fix the problem for the moment. But besides it would be nice if your lib respects deactivated dst in some way. It‘s an official configuration flag in Windows … thus it would be great.