[issue4329] base64 does not properly handle unicode strings

Michael Becker [EMAIL PROTECTED] added the comment: Terry, I had a feeling Django had something to do with this. I'll have a closer look there. For reference, in my django code, I did not explicitly declare the string as a unicode string. Django must be importing unicode_literals from __future__

[issue4329] base64 does not properly handle unicode strings

Michael Becker [EMAIL PROTECTED] added the comment: Terry, Thanks for your response. My main concern was that the behavior changed when updating from 2.5 to 2.6. The new behavior was not intuitive. Also 2.6, I thought, was supposed to be backward compatible. Based on this issue, I would assume

[issue1202] zlib.crc32() and adler32() return value

Michael Becker [EMAIL PROTECTED] added the comment: In case it isn't obvious the work around for pre 3.0 to get the right sum is something like: x=zlib.adler32(str) if x 0: x=(long(x) + 4294967296L) # 2^32, long may or may not be needed here -- nosy: +mbecker