On 12/23/21 07:39, Stephen J. Turnbull wrote:
Hao Hu writes:
> On 12/18/21 08:44, Stephen J. Turnbull wrote:
> > Hao Hu writes:
> > > >> For instance, if we create a caching programming interface that
> > > >> relies on a distributed kv store,
On 12/18/21 08:44, Stephen J. Turnbull wrote:
Hao Hu writes:
> > On 17 Dec 2021, at 15:28, Chris Angelico wrote:
> > The built-in hash() function is extremely generic, so it can't really
> > work that way. Adding a parameter to it would require (a) adding the
>
> On 17 Dec 2021, at 15:49, Chris Angelico wrote:
>
> On Sat, Dec 18, 2021 at 1:44 AM Hao Hu wrote:
>>> For that sort of thing, it may be more practical to use your own
>>> hashing function, possibly a cryptographically secure one. The precise
>>> h
> On 17 Dec 2021, at 15:42, Steven D'Aprano wrote:
>
> On Fri, Dec 17, 2021 at 02:07:38PM -0000, Hao Hu wrote:
>> Hi,
>>
>> I am wondering if it would be good to add an additional keyword `seed`
>> to the builtin function *hash* to allow us to set arbitrar
> On 17 Dec 2021, at 15:28, Chris Angelico wrote:
>
> On Sat, Dec 18, 2021 at 1:21 AM Hao Hu wrote:
>>
>> Hi,
>>
>> I am wondering if it would be good to add an additional keyword `seed` to
>> the builtin function *hash* to allow us to set arbitrary
Hi,
I am wondering if it would be good to add an additional keyword `seed` to the
builtin function *hash* to allow us to set arbitrary seed to ensure
reproducible results.
As far as I know, there exists already the environment variable PYTHONHASHSEED
that allows us to set arbitrary seed or
