[Python-Dev] Locked-in defect? 32-bit hash values on 64-bit builds

Barry Warsaw barry at python.org
Fri Oct 15 20:07:24 CEST 2010

On Oct 15, 2010, at 12:40 PM, Benjamin Peterson wrote:

>2010/10/15 Raymond Hettinger <raymond.hettinger at gmail.com>:
>> After rereading http://bugs.python.org/issue9778 , I'm growing concerned
>> about an impending ABI freeze before the core devs find time to fix the
>> 32-bit hash limitation.
>> ISTM, the use of 64-bit builds is growing in popularity.  It was be a bummer
>> to have a locked-in an effective size limit for dictionaries and sets
>> because
>> the API only supports 32-bit hash values.
>> The thread seems to show agreement that the hash values should be
>> Py_ssize_t but the chance to fix it will be lost unless core devs get
>> more time to work on the problem or unless the ABI freeze is deferred.
>I think the panic is a bit of an overreaction. PEP 384 has still not
>been accepted, and I haven't seen a final decision about freezing the
>ABI in 3.2.

Yes, but there's less than a month left before 3.2 beta 1, and then it *will*
be too late, at least for this release.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/python-dev/attachments/20101015/0616bb3d/attachment.pgp>

More information about the Python-Dev mailing list