bug#22010: bytecode timestamps

2019-02-08 Thread Ricardo Wurmus
Ricardo Wurmus writes: > I’ll push the change to the core-updates branch. This is now on core-updates. Python 2 now builds reproducibly. -- Ricardo

bug#22010: bytecode timestamps

2019-02-05 Thread Ricardo Wurmus
Ricardo Wurmus writes: > I wonder if we can simplify this with (setenv "PYTHONHASHSEED" "0") > before any pyc files are built, but I expect that to be problematic. Doing this has no discernable effect. I’ll push the change to the core-updates branch. -- Ricardo

bug#22010: bytecode timestamps

2019-02-05 Thread Ricardo Wurmus
Leo Famulari writes: > Those differing bytes are the timestamps of the .py sources files that > correspond to the compiled .pyc / .pyo files. So, the > python-2.7-source-date-epoch.patch is working for software compiled by > the patched compiler, but not on python-2.7 itself. > > It's related to

bug#22010: bytecode timestamps

2016-02-07 Thread Leo Famulari
Those differing bytes are the timestamps of the .py sources files that correspond to the compiled .pyc / .pyo files. So, the python-2.7-source-date-epoch.patch is working for software compiled by the patched compiler, but not on python-2.7 itself. It's related to