bug#22533: Non-determinism in python-3 ".pyc" bytecode

2016-04-06 Thread Ludovic Courtès
Cyril Roelandt skribis: > Here is a version of the patch that works with the upstream Python, but > that I cannot get to work with our Guix recipe. At first sight the patch LGTM. How does it not work for you? :-) I applied this: diff --git a/gnu/packages/patches/python-3-deterministic-build-i

bug#22533: Non-determinism in python-3 ".pyc" bytecode

2016-03-29 Thread Cyril Roelandt
Here is a version of the patch that works with the upstream Python, but that I cannot get to work with our Guix recipe. Could you test it and tell me what you think? I intend to push this to CPython. Cyril. diff --git a/Lib/importlib/_bootstrap.py b/Lib/importlib/_bootstrap.py index c4ee41a..d988

bug#22533: Non-determinism in python-3 ".pyc" bytecode

2016-03-29 Thread Cyril Roelandt
Here is a version of the patch that works with the upstream Python, but that I cannot get to work with our Guix recipe. Could you test it and tell me what you think? I intend to push this to CPython. Cyril. diff --git a/Lib/importlib/_bootstrap.py b/Lib/importlib/_bootstrap.py index c4ee41a..d988

bug#22533: Non-determinism in python-3 ".pyc" bytecode

2016-02-04 Thread Leo Famulari
On Tue, Feb 02, 2016 at 09:41:19PM +0100, Ludovic Courtès wrote: > Could you give it a try and refine as needed? :-) I altered your example as shown in the attached patch. It causes some tests related to timestamps to fail, so I disabled them in a very crude way. The final patch should address th

bug#22533: Non-determinism in python-3 ".pyc" bytecode

2016-02-02 Thread Ludovic Courtès
Leo Famulari skribis: > We fixed this in python-2 with the patch > python-2.7-source-date-epoch.patch, but I don't know how to write this > patch for python-3. I would imagine something like this (untested): --- Python-3.4.3/Lib/importlib/_bootstrap.py 2016-02-02 21:38:48.655809055 +0100 +++ Py

bug#22533: Non-determinism in python-3 ".pyc" bytecode

2016-02-02 Thread Leo Famulari
On Tue, Feb 02, 2016 at 12:15:44AM -0500, Leo Famulari wrote: > While preparing a package for borg [0], I found that the built output > was not reproducible. The problem is that the bytecode compiler [1] for > Python 3.4.3 (our current version) encodes the mtime of the > corresponding Python source

bug#22533: Non-determinism in python-3 ".pyc" bytecode

2016-02-01 Thread Leo Famulari
While preparing a package for borg [0], I found that the built output was not reproducible. The problem is that the bytecode compiler [1] for Python 3.4.3 (our current version) encodes the mtime of the corresponding Python source file in the output. This is described in PEP-3147 [2], and the respon