> I plan to commit my fix to Python 3.3 if it is accepted. Then write a
> simplified version to Python 3.2 and backport it to 3.1.

I'm opposed to any change to the hash values of strings in maintenance
releases, so I guess I'm opposed to your patch in principle.

Please at least consider his patch for 3.3 onwards then. �Changing the hash seed per interpreter instance / process is the right thing to do going forward.
">

(original) (raw)


On Tue, Jan 17, 2012 at 12:52 PM, "Martin v. L�wis" <martin@v.loewis.de> wrote:

> I plan to commit my fix to Python 3.3 if it is accepted. Then write a
> simplified version to Python 3.2 and backport it to 3.1.

I'm opposed to any change to the hash values of strings in maintenance
releases, so I guess I'm opposed to your patch in principle.

Please at least consider his patch for 3.3 onwards then. �Changing the hash seed per interpreter instance / process is the right thing to do going forward.

What to do on maintenance releases is a separate discussion.

-gps