Comment 2 for bug 1887664

Revision history for this message
Tiago Stürmer Daitx (tdaitx) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Is there any reason why 'dateutil.tz' can't be used instead of dateutil.zoneinfo? The original bug report was made against python-sqlalchemy-utils, which seems to indicate that some functionatility of it might be making use of dateutil.zoneinfo instead of dateutil.tz.

Some context:
python-dateutil’s zoneinfo tarball is not included in the binary package since 1.4.1-1ubuntu2 (from 28 Sep 2008) [1].

The dateutil.zoneinfo is expected to use the shipped tarball instead of the system’s tzdata. Unfortunately shipping copies zoneinfo data goes against Debian and Ubuntu policies - specially for outdated copies. See the original bug report for that in Debian [2].

The usual way to access timezone data is by relying on dateutil.tz: it is designed to use the system's zoneinfo first, with dateutil.zoneinfo as a fallback. Debian and Ubuntu ship tzdata with current zoneinfo, thus the dateutil.zoneinfo code is never used - it seems it is there basically for Windows, since Windows provides no API for timezone data.

On a side note: PEP 615 [3] has been approved for Python 3.9 and so python-dateutil will no longer be required in the future - there’s also some plans to include it as a backport for 3.6+.

Bug will be marked as incomplete while we wait for more information. Feel free to reply back and change its status after updating the report.

Thanks!

References:
[1] https://launchpad.net/ubuntu/+source/python-dateutil/1.4-1ubuntu2
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416204
[3] https://www.python.org/dev/peps/pep-0615/