Dear Colleagues

Some time ago (2017) I took responsibility for python-tz (now within the
python team).

This essentially wraps timezone and adds a few helper functions, but it
does so taking the original data from a vendored copy of zoneinfo, not
the standard copy on the system, which it pickles into the python modules.

From the timezone "forking saga" (https://lwn.net/Articles/870478/) it
looks like this can lead to divergences of output wrt tzdata; that at
least it needs to build against the "Offical Debian" tzdata and be
tracked with it (including backports).

Are any other packages in the same situation ? What will Debian be doing
wrt Timezone  data ?

Best regards

Alastair

--
Alastair McKinstry, <alastair@sceal.ie>, <mckinstry@debian.org>, https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 9/30/21 10:50, Alastair McKinstry wrote:

Are any other packages in the same situation ?

In pytzdata, I've removed the embedded copy in order to use the system
copy (= tzdata) of the zoneinfo files.

Regards,
Daniel

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 30/09/2021, 18:00, "Daniel Baumann" <daniel.baumann@progress-linux.org> wrote:

On 9/30/21 10:50, Alastair McKinstry wrote:
> Are any other packages in the same situation ?

In pytzdata, I've removed the embedded copy in order to use the system
copy (= tzdata) of the zoneinfo files.

Sensible, I think.

There is an updated python-tz (pytz) today - 2021.3 ; I've adapted the build to use the system copy (tzdata)

Regards,
Daniel

Regards
Alastair

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)