This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author zwol
Recipients dstufft, eric.araujo, zwol
Date 2019-10-29.13:03:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1572354197.87.0.67466678891.issue38632@roundup.psfhosted.org>
In-reply-to
Content
Reproducibility has so far been concerned primarily with binary packages, but it's also desirable for source tarballs to be reproducible starting from a version-control checkout.  This is particularly important for Python, where 'setup.py sdist' can run arbitrary code and generated files (e.g. Cython-generated C) are often included in sdists.

As a small step toward this goal, please add support for the SOURCE_DATE_EPOCH environment variable to distutils.command.sdist.  The most natural way to implement this would be with an additional user option, perhaps called 'timestamp_limit', which takes a date and time argument.  File modification timestamps in the generated tarball or zipfile will be adjusted to be no later than that time.  If 'timestamp_limit' is not set, it defaults to the value of os.environ['SOURCE_DATE_EPOCH'].

The specification for SOURCE_DATE_EPOCH may be found at https://reproducible-builds.org/specs/source-date-epoch/ .
History
Date User Action Args
2019-10-29 13:03:17zwolsetrecipients: + zwol, eric.araujo, dstufft
2019-10-29 13:03:17zwolsetmessageid: <1572354197.87.0.67466678891.issue38632@roundup.psfhosted.org>
2019-10-29 13:03:17zwollinkissue38632 messages
2019-10-29 13:03:17zwolcreate