From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Cc: Brian Inglis <Brian.Inglis@shaw.ca>
Subject: Re: deprecate pytz? or update pytz to 2022g/2022.7.1
Date: Wed, 8 Mar 2023 06:11:46 +0100 [thread overview]
Message-ID: <86bc278d-35df-1fe6-7fd2-94e61613427f@gmail.com> (raw)
In-Reply-To: <CAB8Xom8_0UT9NKogHoQMgBuLfU+iDcWgHr3my1LevE4y+AgpPw@mail.gmail.com>
On 07.03.2023 22:35, marco atzeri wrote:
> On Tue, Mar 7, 2023 at 10:18 PM Brian Inglis via Cygwin < wrote:
>>
>> On 2022-03-20 10:00, Brian Inglis wrote:
>>> On 2021-12-21 09:06, Marco Atzeri via Cygwin-announce wrote:
>>>> Several python packages have been added to the Cygwin distribution
>>>> and at the same time the updated packages for 3.6/3./3.8
>>>> have been uploaded.
>>>> python39-pytz 2021.3-1
>>
>
>>
>> Update needed to 2022g/2022.7.1 as a new Mexican zone was added since
>> 2021c/2021.3 due to Mexican changes conflicting with US practices, affecting
>> border towns:
>>
>
> noted
Hi Brian
2022.7.1 is up
Regards
Marco
next prev parent reply other threads:[~2023-03-08 5:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 16:06 [ANNOUNCEMENT] Updated: python 3.9 packages Marco Atzeri via Cygwin-announce
2021-12-22 13:52 ` airplanemath
2021-12-23 20:00 ` Marco Atzeri
2021-12-24 10:57 ` Jon Turney
2021-12-24 11:16 ` Marco Atzeri
2021-12-24 13:53 ` Jon Turney
2021-12-23 20:34 ` Russell VT
2021-12-24 6:57 ` Marco Atzeri
2022-03-20 16:00 ` deprecate pytz? Brian Inglis
2023-03-07 21:18 ` deprecate pytz? or update pytz to 2022g/2022.7.1 Brian Inglis
2023-03-07 21:35 ` marco atzeri
2023-03-08 5:11 ` Marco Atzeri [this message]
2023-03-26 20:45 ` update pytz to 2023.2/2023b tzdata Brian Inglis
2023-03-27 0:13 ` update pytz to 2023.2/2023b tzdata? Brian Inglis
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=86bc278d-35df-1fe6-7fd2-94e61613427f@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=Brian.Inglis@shaw.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).