From: "KAVALAGIOS Panagiotis (EEAS-EXT)" <Panagiotis.KAVALAGIOS@ext.eeas.europa.eu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Python for Windows reports wrong local time when run under Cygwin on Europe/Moscow TZ
Date: Thu, 10 Jun 2021 15:25:53 +0000 [thread overview]
Message-ID: <cc5fdd94b40443c0b8cbccea0955f761@BELBRU-EXMP101.eeas.europa.eu> (raw)
In-Reply-To: <0fcfeb54-53c5-b83d-bb13-e83a68eed469@cornell.edu>
> -----Original Message-----
> Behalf Of Ken Brown via Cygwin
> Sent: 10 June 2021 16:58
> Subject: Re: Python for Windows reports wrong local time when run under
> Cygwin on Europe/Moscow TZ
>
> I'm not convinced it's worth the trouble. I haven't seen anyone argue that
> it's useful for Cygwin to set TZ, and I have seen an argument that it's harmful:
>
> https://cygwin.com/pipermail/cygwin/2017-May/232675.html .
>
> So I prefer Keith's second suggestion:
>
> >> - Cygwin shouldn't set TZ at all by default.
I also support that TZ environmental variable shouldn't be set by default in Cygwin. I don't even remember any Solaris, HP-UX, IRIX, Digital Unix, FreeBSD, Linux etc. setting it by default. It was up to the user to define it and enjoy with the different output of the "date" command.
It might have been introduced in Cygwin to resolve some issues on the programs that need POSIX TZ format, but for the rest of the programs that still consult the windows format will fail. It would be more reasonable to use a wrapper script for those programs that have issues to set it explicitly to the expected windows default format.
Kind regards,
Panos Kavalagios
Application Architect
CONSULIAT (under contract with the EEAS)
BA.BS.3.IS
Office: EEAS B100 Floor 5 Area 048
Rue Belliard 100, 1000 Brussels
Phone: +32 2 584 6017
next prev parent reply other threads:[~2021-06-10 15:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
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) [this message]
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=cc5fdd94b40443c0b8cbccea0955f761@BELBRU-EXMP101.eeas.europa.eu \
--to=panagiotis.kavalagios@ext.eeas.europa.eu \
--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).