-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
InsertDate ignores change of system timezone #33
Labels
Comments
vovkkk
changed the title
Upstream pytz bug: Novosibirsk must be UTC+7
InsertDate ignores change of system timezone
Jul 24, 2016
Actually this is not the point (original report). The point is that if you change timezone of your OS, then you have to restart ST to make InsertDate show correct time. |
What OS is this on? I wonder if this is something I can actually fix. |
Windows 8.1 Enterprise 32bit |
vovkkk
added a commit
to vovkkk/InsertDate
that referenced
this issue
Nov 26, 2016
the problem described in FichteFoll#33 is caused by datetime module itself; thus for reliability and user convenience it can be monkey-patched relatively simple
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This happened unexpectedly: our local parliament decided to change time zone; they took decision just in July, and it became legit this night; I knew about it just hour ago.
Crazy stuff.
Steps to reproduce:
"tz_in": "Asia/Novosibirsk"
Expected result
UTC+7, e.g. 14:50
Actual
UTC+6, 13:50
The text was updated successfully, but these errors were encountered: