From: Russell VT <russellvt@gmail.com>
To: Mike Kaganski <mikekaganski@mail.ru>
Cc: cygwin@cygwin.com
Subject: Re: Python for Windows reports wrong local time when run under Cygwin on Europe/Moscow TZ
Date: Mon, 7 Jun 2021 21:34:45 -0700 [thread overview]
Message-ID: <CANV2+nXndvbu9_Ey2W8zbC-OdVkV0ZGmo4ZUvHH1fA+wen5PvA@mail.gmail.com> (raw)
In-Reply-To: <5542c19d-8b1a-1f28-2003-fe9493ee9b56@mail.ru>
What version(s) of the timezone files are installed on each?
Also, seems one of the Python versions came from Windows, rather than
Cygwin?
On Mon, Jun 7, 2021 at 12:01 AM Mike Kaganski via Cygwin <cygwin@cygwin.com>
wrote:
> Hello,
>
> Running Cygwin 3.1.7-1 on Windows 10 Version 21H1 (OS Build 19043.985),
> I have this issue:
>
> when I start Cygwin's Python, I have correct time reported:
>
> > mikek@DESKTOP-8SHAE9Q ~
> > $ python
> > Python 3.8.9 (default, Apr 21 2021, 23:14:29)
> > [GCC 10.2.0] on cygwin
> > Type "help", "copyright", "credits" or "license" for more information.
> > >>> import datetime
> > >>> datetime.datetime.now()
> > datetime.datetime(2021, 6, 7, 9, 40, 15, 318391)
>
> 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:
>
> > mikek@DESKTOP-8SHAE9Q ~
> > $ "C:/Program
> >
> Files/WindowsApps/PythonSoftwareFoundation.Python.3.8_3.8.2800.0_x64__qbz5n2kfra8p0/python3.8.exe"
> > Python 3.8.10 (tags/v3.8.10:3d8993a, May 3 2021, 11:48:03) [MSC
> > v.1928 64 bit (AMD64)] on win32
> > Type "help", "copyright", "credits" or "license" for more information.
> > >>> import datetime
> > >>> datetime.datetime.now()
> > datetime.datetime(2021, 6, 7, 7, 40, 55, 503775)
>
> Note how the latter output reports 2021-06-07 07:40, while the former
> reports 2021-06-07 09:40. The difference is 2 hours.
>
> Starting the same Python for Windows from cmd.exe has it correct:
>
> > C:\Users\mikek>python
> > Python 3.8.10 (tags/v3.8.10:3d8993a, May 3 2021, 11:48:03) [MSC
> > v.1928 64 bit (AMD64)] on win32
> > Type "help", "copyright", "credits" or "license" for more information.
> > >>> import datetime
> > >>> datetime.datetime.now()
> > datetime.datetime(2021, 6, 7, 9, 41, 21, 925240)
>
> Cygwin reports correct timezone:
>
> > $ echo $TZ
> > Europe/Moscow
>
> Starting Python for Windows using a different timezone (specifically, '$
> TZ=UTC "C:/Program
> Files/WindowsApps/PythonSoftwareFoundation.Python.3.8_3.8.2800.0_x64__qbz5n2kfra8p0/python3.8.exe"')
>
> gives correct time for *that* time zone.
>
> 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 (from 00:00 till
> 02:00) it reports wrong dates, which makes tests fail locally on
> affected systems(see [2]).
>
> Thank you!
>
>
> [1] https://www.microsoft.com/en-us/p/python-38/9mssztt1n39l
>
> [2]
>
> https://gerrit.libreoffice.org/c/core/+/92217/2#message-f55091795e7cde9d75adc00ddb69451121b644f6
>
>
> --
>
> Best regards,
>
> Mike Kaganski
>
>
> --
> Problem reports: https://cygwin.com/problems.html
> FAQ: https://cygwin.com/faq/
> Documentation: https://cygwin.com/docs.html
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
>
--
Russell M. Van Tassell <russellvt@gmail.com>
next prev parent reply other threads:[~2021-06-08 4:35 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 [this message]
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
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=CANV2+nXndvbu9_Ey2W8zbC-OdVkV0ZGmo4ZUvHH1fA+wen5PvA@mail.gmail.com \
--to=russellvt@gmail.com \
--cc=cygwin@cygwin.com \
--cc=mikekaganski@mail.ru \
/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).