From: Keith Thompson <Keith.S.Thompson@gmail.com>
To: cygwin@cygwin.com
Cc: Keith Thompson <Keith.S.Thompson@gmail.com>
Subject: Re: Python for Windows reports wrong local time when run under Cygwin on Europe/Moscow TZ
Date: Tue, 8 Jun 2021 10:37:37 -0700 [thread overview]
Message-ID: <CAAHpriO6A+6bLXt0Qe-xpdXT1CiLjk7=7G31cHBtnVJ0kXb2Eg@mail.gmail.com> (raw)
There is a known problem with the $TZ environment variable.
Here's a discussion from 2017:
https://cygwin.com/pipermail/cygwin/2017-May/232675.html
The problem is that both Cygwin and Windows use the $TZ environment
variable, but they interpret it differently.
The Windows handling of $TZ (or %TZ%) is documented here:
https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/tzset?view=msvc-160
For example, Pacific Time is represented as TZ=PST8PDT.
In Cygwin, my $TZ is set by default to "America/Los_Angeles".
Any Windows applications that I invoke from Cygwin, if they attempt
to determine the time zone, will behave inconsistently because they
don't see "America/Los_Angeles" as a valid time zone string.
I've worked around this by unsetting TZ in my .bash_profile .
Cygwin applications are still able to determine the correct time zone.
I suggest that Cygwin should *not* set the TZ environment variable.
next reply other threads:[~2021-06-08 17:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 17:37 Keith Thompson [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2021-06-07 6:59 Mike Kaganski
2021-06-08 4:34 ` Russell VT
2021-06-08 7:51 ` Mike Kaganski
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
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='CAAHpriO6A+6bLXt0Qe-xpdXT1CiLjk7=7G31cHBtnVJ0kXb2Eg@mail.gmail.com' \
--to=keith.s.thompson@gmail.com \
--cc=cygwin@cygwin.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).