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 WaylandZ
Recipients WaylandZ
Date 2017-08-31.08:15:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1504167349.56.0.0314062412353.issue31312@psf.upfronthosting.co.za>
In-reply-to
Content
When I build python (version 2.7.13), I find the build results are different every time. It seems to be caused by some times tamps, and they may be generated by the code below:
    Lib/py_compile.py:106: with open(file, 'U') as f:
    Lib/py_compile.py:107:     try:
    Lib/py_compile.py:108:        timestamp = long(os.fstat(f.fileno()).st_mtime)
    Lib/py_compile.py:109:    except AttributeError:
    Lib/py_compile.py:110:        timestamp = long(os.stat(file).st_mtime)
    Lib/py_compile.py:111:   codestring = f.read()

As we know, reproducible build is a good way to counter malicious attacks that generate malicious executables, by making it easy to recreate the executable to determine if the result is correct. How can I eliminate the differences caused by the time stamps? Just remove some code? Or is there any configuration?
If we can't eliminate the difference now, can lsof support it in future versions?
Thank you.
History
Date User Action Args
2017-08-31 08:15:49WaylandZsetrecipients: + WaylandZ
2017-08-31 08:15:49WaylandZsetmessageid: <1504167349.56.0.0314062412353.issue31312@psf.upfronthosting.co.za>
2017-08-31 08:15:49WaylandZlinkissue31312 messages
2017-08-31 08:15:48WaylandZcreate