On 11/16/20 9:57 AM, Filipe Laíns wrote: > 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 opened a bug on the tracker including a patch: https://bugs.archlinux.org/task/68642?project=1&string=python I do think it makes sense to make it a direct dependency, since I personally worry that transitive dependencies may be fragile (and even if the transitive dependency is rock-solid, it doesn't hurt anything for it to exist — plus it gives you metadata about what projects are using what packages, for purposes of notifying or looking for issues). That said, it's obviously up to y'all. There's actually another thing that is probably of interest to distro packagers, which is that zoneinfo includes a compile-time configuration option: https://docs.python.org/3/library/zoneinfo.html#zoneinfo-data-compile-time-config By default we don't know where the zoneinfo will be deployed, so we use a set of locations where it's commonly deployed. Since distro packagers know exactly where it is deployed, they can use the `--with-tzpath` configuration option to specify it at build time, to make the lookup that much faster and more accurate. > 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]. Yeah, I was mainly looking for a way to contact all of them at once, since it doesn't scale very well for me to open bugs on the trackers of every distributor. I can open bugs for my distro and distros that I care about, but even that can be pretty duplicative. > Maybe it would make sense to create a community mailing list for > packagers? That sounds like a good idea to me. > 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. This also seems like a good idea to me (though I'm not entirely sure how often packagers are impacted by changes to CPython — zoneinfo may have been an unusual case). Best, Paul
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 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/74KJJM6ZGHVV2RADCTZLVAKY7VO5KIG2/ Code of Conduct: http://python.org/psf/codeofconduct/
