Guido van Rossum <guido@python.org> wrote:
> ISTM the only reasonable thing is to have a random seed picked very early
> in the process, to be used to change the hash() function of
> str/bytes/unicode (in a way that they are still compatible with each other).

Do str and bytes still have to be compatible with each other in 3.x?

Hm, you're right, that's no longer a concern. (Though ATM the hashes still *are* compatible.)
�
">

(original) (raw)

On Sat, Dec 31, 2011 at 9:11 PM, Antoine Pitrou <solipsis@pitrou.net> wrote:

On Sat, 31 Dec 2011 16:56:00 -0700

Guido van Rossum <guido@python.org> wrote:
> ISTM the only reasonable thing is to have a random seed picked very early
> in the process, to be used to change the hash() function of
> str/bytes/unicode (in a way that they are still compatible with each other).

Do str and bytes still have to be compatible with each other in 3.x?

Hm, you're right, that's no longer a concern. (Though ATM the hashes still \*are\* compatible.)
�

Merry hashes, weakrefs and thread-local memoryviews to everyone!


:-)
�
--
--Guido van Rossum (python.org/~guido)