This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients belopolsky, benjamin.peterson, casevh, georg.brandl, jimjjewett, ked-tao, lemburg, loewis, mark.dickinson, pitrou, rhettinger, skip.montanaro, tim.peters
Date 2010-10-18.15:27:26
SpamBayes Score 0.0030310224
Marked as misclassified No
Message-id <1287415644.3492.5.camel@localhost.localdomain>
In-reply-to <>
> AFAICT, a change from (Py_ssize_t)-1 to (size_t)-1 is less likely to
> break code than a change from -1L to  (Py_ssize_t)-1.  (Assuming a
> sizeof(long) != sizeof(void*) platform.)

That's true.

> The benefit, though is that
> hash computations can be performed natively on the hash values without
> casting to an unrelated type.

I don't understand what you mean by "native" and "unrelated". Signed
integers are not less native than unsigned ones.
Date User Action Args
2010-10-18 15:27:28pitrousetrecipients: + pitrou, lemburg, tim.peters, loewis, skip.montanaro, georg.brandl, rhettinger, jimjjewett, mark.dickinson, belopolsky, casevh, ked-tao, benjamin.peterson
2010-10-18 15:27:27pitroulinkissue9778 messages
2010-10-18 15:27:26pitroucreate