Author steven.daprano
Recipients Dima.Tisnek, benjamin.peterson, steven.daprano
Date 2018-12-28.07:09:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20181228070912.GE13616@ando.pearwood.info>
In-reply-to <1545969866.26.0.69260487679.issue35600@roundup.psfhosted.org>
Content
> Steven, my requirement calls for same hash on multiple machines. 
> Python's hash (for strings) is keyed with a random value.

Ah, of course it does, I forgot about that.

The only problem with exposing siphash is that we are exposing a private 
implementation detail (the specific hash function used) as a public 
interface. That means that we'd need to keep siphash forever, even if we 
want to use a different hash function in the future.

Now maybe we're willing to do that, perhaps exposing it through the 
hashlib module, with no guarantee that it is related in any way to what 
hash() calls. But I think now we're moving in Python-Ideas mailing list 
territory, and as Benjamin points out, there is a third-party library.
History
Date User Action Args
2018-12-28 07:09:20steven.dapranosetrecipients: + steven.daprano, benjamin.peterson, Dima.Tisnek
2018-12-28 07:09:18steven.dapranolinkissue35600 messages
2018-12-28 07:09:18steven.dapranocreate