public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: 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 23:50:12 -0600	[thread overview]
Message-ID: <92dc21ea-0975-2c58-5c5c-f3d8962d34c6@SystematicSw.ab.ca> (raw)
In-Reply-To: <daa04160-a8ad-ac49-5d19-b99c17e93d8a@mail.ru>

On 2021-06-08 14:03, Mike Kaganski via Cygwin wrote:
> On 08.06.2021 16:04, L A Walsh wrote:
>> You might ask on a python list if anyone else has experienced
>> something similar with python or any other program.  I'm fairly sure
>> that neither MS nor cygwin design their OS with python in mind and
>> that it is python that is interacting funny when running under some
>> merge of both.  Have you asked the python people about this problem?
>> What did they suggest? 
> 
> FTR: filed https://bugs.python.org/issue44352.

See Keith Thompson subthread and my reply with suggested fix:

	https://cygwin.com/pipermail/cygwin/2021-June/248692.html

Windows does not recognize zoneinfo time zone identifiers in TZ only 
base format POSIX TZ strings with three alphabetic character identifiers:

	https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/tzset?view=msvc-160

That assumes US switch date "rules": for all years up to current, or 
just DST, and whether pre- or post-2007 is unstated!

Otherwise it defaults to regional settings, used by Cygwin to map to 
zoneinfo time zone identifiers, so if Python for Windows could clear TZ 
before it is read by MSVCRT, it should DTRT.

Windows does not recognize expanded POSIX TZ format strings with <> 
quoted alphanumeric characters, "-", "+", and start and end dates/times:

	https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html#bottom

which make them usable outside of the US.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2021-06-09  5:50 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
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 [this message]
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=92dc21ea-0975-2c58-5c5c-f3d8962d34c6@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).