[Python-Dev] Converting crc32 functions to use unsigned

2006-05-30 Thread Bob Ippolito
It seems that we should convert the crc32 functions in binascii, zlib, etc. to deal with unsigned integers. Currently it seems that 32- bit and 64-bit platforms are going to have different results for these functions. Should we do the same as the struct module, and do DeprecationWarning

Re: [Python-Dev] Converting crc32 functions to use unsigned

2006-05-30 Thread Guido van Rossum
Seems ok, except I don't know what the backwards incompatibilities would be... On 5/30/06, Giovanni Bajo [EMAIL PROTECTED] wrote: Bob Ippolito wrote: It seems that we should convert the crc32 functions in binascii, zlib, etc. to deal with unsigned integers. +1!! -- --Guido van Rossum

Re: [Python-Dev] Converting crc32 functions to use unsigned

2006-05-30 Thread Bob Ippolito
On May 30, 2006, at 11:19 AM, Guido van Rossum wrote: On 5/30/06, Giovanni Bajo [EMAIL PROTECTED] wrote: Bob Ippolito wrote: It seems that we should convert the crc32 functions in binascii, zlib, etc. to deal with unsigned integers. +1!! Seems ok, except I don't know what the backwards

Re: [Python-Dev] Converting crc32 functions to use unsigned

2006-05-30 Thread Tim Peters
[Bob Ippolito] It seems that we should convert the crc32 functions in binascii, zlib, etc. to deal with unsigned integers. Currently it seems that 32- bit and 64-bit platforms are going to have different results for these functions. binascii.crc32 very deliberately intends to return the same