If gzip is modified to use SOURCE_DATE_EPOCH timestamp, you get a reproducible binary and you don't need to add a new constant ;-) SOURCE_DATE_EPOCH is a timestamp: number of seconds since Unix Epoch (January 1, 1970 at 00:00).
Victor On Wed, Apr 14, 2021 at 8:15 PM <j.wut...@fz-juelich.de> wrote: > > The gzip specification [1] makes clear that the mtime field is always present. > The time is in Unix format, i.e., seconds since 00:00:00 GMT, Jan. 1, 1970. > MTIME = 0 means no time stamp is available. Hence no need for a > new constant NO_TIMESTAMP. > > So this is primarily a documentation problem [2]. For this, I will create a > pull request to gzip.py. > > Joachim > > [1] https://www.ietf.org/rfc/rfc1952.txt > [2] > https://discuss.python.org/t/gzip-py-allow-deterministic-compression-without-time-stamp > _______________________________________________ > 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/LCPWERWIFG4AJS6DPHNEMOGBYJ2APDJ3/ > Code of Conduct: http://python.org/psf/codeofconduct/ -- Night gathers, and now my watch begins. It shall not end until my death. _______________________________________________ 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/FZTBVELC53IX6CGRCG53IGECJC3SANLE/ Code of Conduct: http://python.org/psf/codeofconduct/
