public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Subject: Re: deprecate pytz? or update pytz to 2022g/2022.7.1
Date: Tue, 7 Mar 2023 14:18:05 -0700	[thread overview]
Message-ID: <f3809999-d6e8-b5df-13c1-2456ff86c530@Shaw.ca> (raw)
In-Reply-To: <1361c3e8-113b-9855-6afb-c7c3b1d0c20e@SystematicSw.ab.ca>

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

> Suggesting that pytz should be deprecated and eventually dropped.
> There is a lot of discussion on the IANA TZ mailing list about support of the 
> IANA TZ DB (tzdata) in languages other than C, and there has been discussion of 
> the official python standard library module support of tzdata, and the problems 
> of correctly using pytz:
>	https://blog.ganssle.io/articles/2018/03/pytz-fastest-footgun.html
> requiring close reading and following of its limitations:
>	https://pypi.org/project/pytz/
>	https://github.com/stub42/pytz
> together with it being superceded by official support of IANA TZ DB with a 
> standard library compiled zoneinfo module built on the datetime module:
>	https://peps.python.org/pep-0615/
> backported to 3.6+ as the backports.zoneinfo module:
>	https://zoneinfo.readthedocs.io/en/latest/
>	https://github.com/pganssle/zoneinfo/

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:

	https://mm.icann.org/pipermail/tz-announce/2022-November/000076.html

"The 2022g release of the tz code and data is available.

  This release contains the following changes:

       Briefly:
	The northern edge of Chihuahua changes to US timekeeping.
...

       Changes to future timestamps

	In the Mexican state of Chihuahua, the border strip near the US
	will change to agree with nearby US locations on 2022-11-30.
	The strip's western part, represented by Ciudad Juárez, switches
	from -06 all year to -07/-06 with US DST rules, like El Paso, TX.
	The eastern part, represented by Ojinaga, will observe US DST next
	year, like Presidio, TX.  (Thanks to Heitor David Pinto.)
	A new Zone America/Ciudad_Juarez splits from America/Ojinaga."

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

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

  reply	other threads:[~2023-03-07 21:18 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   ` Brian Inglis [this message]
2023-03-07 21:35     ` deprecate pytz? or update pytz to 2022g/2022.7.1 marco atzeri
2023-03-08  5:11       ` Marco Atzeri
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=f3809999-d6e8-b5df-13c1-2456ff86c530@Shaw.ca \
    --to=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).