On Mon, 2020-11-16 at 09:32 -0500, Paul Ganssle wrote: Hi all, One part of PEP 615 (IANA time zones) that I expected to be easily overlooked (a point about which I seem to have been right) is the recommendation that starting with Python 3.9, distros should add a dependency on the system time zone data to the Python package. Quoting the PEP: > > Python distributors are encouraged to ensure that time zone data is > installed alongside Python whenever possible (e.g. by declaring > tzdata as a dependency for the python package). > https://www.python.org/dev/peps/pep-0615/#system-time-zone-information I am not sure what is the best way to reach the largest number of distro packagers to suggest that they add a dependency on tzdata for Python 3.9+, so I figured I'd send a message here. If you know a distro packager who does not follow this list, or you use a distro that doesn't have a dependency on tzdata for Python 3.9, please forward this e-mail to them and/or open a bug on their issue tracker. So far I know conda-forge got the dependency right from the first Python 3.9 release, Fedora has plans to fix this, and Christian Heimes has opened a bug on the Ubuntu launchpad for this. I will figure out how best to notify Arch Linux and do that (since that's the distro I use). I suspect this will be most important for distros that are heavily used in containers, since tzdata is a common enough dependency that it's likely to be satisfied accidentally in most full-featured user environments anyway. Thanks! Paul P.S. If there's a mailing list or other community for Python distro packagers, please let me know, because I often find that we're making decisions that affect them that they don't hear about until way down the line. I'd love to have an easy way to keep them in the loop.
Hi, In Arch Linux, tzdata is a dependency of glibc, which is part of the base[1] package that should be present on every installation. So, there is no action necessary :) We could make it an explicit dependency, but that it not necessarily required, it is up to the maintainer, whom I have notified. I would say the best approach to reach distro packages is to open a bug in their issue tracker, or to reach them via mailing list. Some of them have specific mailing lists for Python, Fedora has python-devel[2]. Maybe it would make sense to create a community mailing list for packagers? I would also suggest to in the future maybe have a "For packagers" section, or similar, in the release notes. I don't think right now there is any reasonable way packagers could have known about this new dependency unless they are involved with the Python upstream. All the current changelog does is link to PEP 615, where that information is present, but it has no mention of new dependencies. Please let me know if I've overlooked something :P [1] https://www.archlinux.org/packages/core/any/base/ [2] https://lists.fedoraproject.org/archives/list/python-devel%40lists.fedoraproject.org/ Cheers, Filipe Laíns
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/NRAK5GRLCMYGRK4KGJSCXASYNCZ5PZWV/ Code of Conduct: http://python.org/psf/codeofconduct/
