> why is this dependency needed? The tzdata package is marked with Priority > required. See Debian policy 2.5. > > Matthias
Not to put words in Barry's mouth, but I took Barry's comment to be more an answer to the question of how to contact "distro packagers" as a group, more than he was taking a position about this particular issue. That said, as I mentioned on the launchpad <https://bugs.launchpad.net/ubuntu/+source/python3.9/+bug/1904271/comments/4> and elsewhere in this thread, I think that, in general, it makes sense to have an explicit dependency on tzdata as a clear indicator that we actually have a direct dependency on tzdata, even if it's not technically required because it's satisfied automatically for some reason. It would make it easier for people to find packages that depend on tzdata to notify us of issues (I've done something like this before — `tzlocal` is planning to make a backwards-incompatible change to using `zoneinfo`, and when I found out about this I dug up all the projects I could find that explicitly depend on `tzlocal` to notify them of the upcoming change). It also is less fragile. As Christian mentioned in the launchpad issue, zoneinfo is actually broken without a direct dependency on tzdata in the ubuntu docker container — possibly that's a bug in the way the ubuntu docker contianer is packaged, but it wouldn't be a problem for /us/ if python had a dependency on tzdata. As far as I can tell it also wouldn't hurt anything for this dependency to be made explicit rather than implicit. That said — it's entirely up to individual package maintainers how they want to handle their dependency metadata. The important thing I wanted to convey to distro maintainers is that PEP 615 effectively is saying that Python now depends on the system metadata package being present. If there's no need to do anything because tzdata is an implicit dependency for the entire Debian ecosystem then that's fine. Best, Paul On 11/16/20 2:15 PM, Matthias Klose wrote: > On 11/16/20 6:46 PM, Barry Warsaw wrote: >> That’s what I was going to suggest. I’m not doing any Debian or Ubuntu work >> these days, but Matthias Klose should be watching both lists, and should be >> able to handle the Debuntu stack. > >> -Barry >> >>> On Nov 16, 2020, at 07:45, Miro Hrončok <mhron...@redhat.com> wrote: >>> >>> On 11/16/20 4:10 PM, Paul Ganssle wrote: >>>>> Maybe it would make sense to create a community mailing list for >>>>> packagers? >>>> That sounds like a good idea to me. >>> I am following the Linux SIG mailing list. But it's mostly dead. >>> >>> https://mail.python.org/archives/list/linux-...@python.org/ >>> >>> -- >>> Miro Hrončok >>> -- >>> Phone: +420777974800 >>> IRC: mhroncok >>> _______________________________________________ >>> 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/DF3UXOGYRAIOLTRGSNGNSZEKZOUFMXGA/ >>> Code of Conduct: http://python.org/psf/codeofconduct/ >> >> _______________________________________________ >> 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/23R5ZD5ZVA4R73ZTKQWWJR6CDLGRKXJN/ >> Code of Conduct: http://python.org/psf/codeofconduct/ >> > _______________________________________________ > 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/MF4J5HIBM37NRZ5I2RSXYLU7PIXVKXO2/ > Code of Conduct: http://python.org/psf/codeofconduct/
_______________________________________________ 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/CYYMZFSJ4IAI3FDJCFNIMFWJLXFNDXJ5/ Code of Conduct: http://python.org/psf/codeofconduct/
