On Apr 09, 2016, at 08:11 PM, Julien Cristau wrote:
>FWIW I think that's a bad idea. A number of packages run their test
>suite at build time, and running the tests with hash randomization
>enabled seems to me like something we shouldn't give up.
Completely agreed. Although we're in the long ta
On Sat, Apr 9, 2016 at 13:25:39 -0400, Cara wrote:
> I think a better solution is disabling hash randomization by setting
> PYTHONHASHSEED=0 when building Python packages with CPython for Debian,
> probably somewhere in dh-python. Note that this isn't necessary for
> PyPy, which doesn't have has
I've been investigating why some Python packages are unreproducible[1]
and have discovered that in some cases the problem can be traced to
CPython's hash randomization. This happens any time a package writes
files that depend on the iteration order over dictionaries or sets. An
example is python-p
3 matches
Mail list logo