From: Mike Kaganski <mikekaganski@mail.ru>
To: Russell VT <russellvt@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: Python for Windows reports wrong local time when run under Cygwin on Europe/Moscow TZ
Date: Tue, 8 Jun 2021 10:51:03 +0300 [thread overview]
Message-ID: <fe8959f7-e496-104e-4dd5-4b091966c50c@mail.ru> (raw)
In-Reply-To: <CANV2+nXndvbu9_Ey2W8zbC-OdVkV0ZGmo4ZUvHH1fA+wen5PvA@mail.gmail.com>
On 08.06.2021 7:34, Russell VT wrote:
> What version(s) of the timezone files are installed on each?
Cygwin:
> $ cygcheck -c | grep tz
> tzcode 2021a-1 OK
> tzdata 2021a-1 OK
Windows:
I didn't find a TZ-specific update KB in the list of installed updates.
However, I did check that there is a "(UTC+2:00) Juba" timezone in the
Windows selector, as described in [1], which means that the respective
TZ update (also described in KB4601275) is present on system.
>
> Also, seems one of the Python versions came from Windows, rather than
> Cygwin?
Heh, I hoped that when I titled the original mail as "Python *for
Windows* reports ... under Cygwin ...", and repeatedly mentioned that in
the body, it's obvious that indeed, the problem is exactly running
native Windows build of Python under cygwin:
>
> But running Python *for Windows* (it doesn't matter which,
> specifically
> for the test I used the one *from MS Store* [1]), I have incorrect
> local time:
> ...
> Starting the same Python *for Windows* from cmd.exe has it correct:
> ...
> This is a problem, because in our project (LibreOffice), we use
> Cygwin
> as environment for unit testing, where LibreOffice's own Python (also
> *built natively for Windows*) is used, and at some times ...
>
[1]
https://techcommunity.microsoft.com/t5/daylight-saving-time-time-zone/2021-time-zone-updates-for-republic-of-south-sudan-now-available/ba-p/2234981
--
Best regards,
Mike Kaganski
next prev parent reply other threads:[~2021-06-08 7:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 6:59 Mike Kaganski
2021-06-08 4:34 ` Russell VT
2021-06-08 7:51 ` Mike Kaganski [this message]
2021-06-08 11:37 ` L A Walsh
2021-06-08 12:28 ` Mike Kaganski
2021-06-08 13:04 ` L A Walsh
2021-06-08 13:30 ` Mike Kaganski
2021-06-08 13:57 ` L A Walsh
2021-06-08 14:10 ` Mike Kaganski
2021-06-08 14:15 ` L A Walsh
2021-06-08 13:36 ` Mike Kaganski
2021-06-08 20:03 ` Mike Kaganski
2021-06-09 5:50 ` Brian Inglis
2021-06-11 6:01 ` Mike Kaganski
2021-06-08 17:37 Keith Thompson
2021-06-09 3:43 ` Brian Inglis
2021-06-09 22:31 ` Keith Thompson
2021-06-10 2:36 ` Brian Inglis
2021-06-10 14:57 ` Ken Brown
2021-06-10 15:25 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2021-06-10 18:31 ` Brian Inglis
2021-06-10 19:50 ` Ken Brown
2021-06-11 5:38 ` ASSI
2021-06-11 13:38 ` Ken Brown
2021-06-11 17:33 ` Brian Inglis
2021-06-11 18:05 ` Ken Brown
2021-06-12 16:34 ` Brian Inglis
2021-06-12 22:44 ` Ken Brown
2021-06-11 10:51 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe8959f7-e496-104e-4dd5-4b091966c50c@mail.ru \
--to=mikekaganski@mail.ru \
--cc=cygwin@cygwin.com \
--cc=russellvt@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).