Thanks for the clarification. I'm glad we can keep hash randomization
disabled during our builds.
On Fri, May 12, 2017 at 5:22 PM, Guido van Rossum wrote:
> Don't worry, the PYTHONHASHSEED setting does not get recorded in the
> bytecode header and the generated bytecode (even if it sometimes dif
Don't worry, the PYTHONHASHSEED setting does not get recorded in the
bytecode header and the generated bytecode (even if it sometimes differs in
trivial ways) is usable with all hash seed settings.
--Guido
On Fri, May 12, 2017 at 6:06 AM, Freddy Rietdijk
wrote:
> Hi,
>
> On Nix we set PYTHONHAS
Hi,
On Nix we set PYTHONHASHSEED to 0 when building packages, disabling hash
randomization. We do this to improve determinism of the builds because we
store the bytecode next to the code.
When one runs Python directly or via a script PYTHONHASHSEED is not set
thus enabling hash randomization. Am
