So I'm guessing this is failing for users who now have Europe/Kyiv set, and pytz/python-tz/python3-tz cannot find it?
The update in tzdata was to link the old name Europe/Kiev, so I think that should be a workaround for now?
We can certainly try to cherry-pick the Kiev->Kyiv rename. But separately I wonder if this needs fixing "properly" by avoiding the use of embedded code like this, or if that wouldn't be practical for some reason.
Looks like this was "fixed" upstream by updating the embedded database by pulling in IANA 2022b at https:/ /git.launchpad. net/pytz/ commit/ ?id=fbe098e6d2f 78765821c2688fd 00db8dab40bbef
So I'm guessing this is failing for users who now have Europe/Kyiv set, and pytz/python- tz/python3- tz cannot find it?
The update in tzdata was to link the old name Europe/Kiev, so I think that should be a workaround for now?
We can certainly try to cherry-pick the Kiev->Kyiv rename. But separately I wonder if this needs fixing "properly" by avoiding the use of embedded code like this, or if that wouldn't be practical for some reason.