[issue4903] binascii.crc32() - document signed vs unsigned results

Gregory P. Smith added the comment: and r69161, r69160, r69162, r69163, r69164. -- resolution: -> fixed status: open -> closed versions: +Python 2.7, Python 3.1 ___ Python tracker _

[issue4903] binascii.crc32() - document signed vs unsigned results

Gregory P. Smith added the comment: wording updated in r69159, thanks. ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue4903] binascii.crc32() - document signed vs unsigned results

Gabriel Genellina added the comment: Just a small note on the wording: "will have" and "will always be" look too strong to me. I'd just use is, are. Present tense seems to be --in general-- the preferred style in the documentation. -- nosy: +gagenellina __

[issue4903] binascii.crc32() - document signed vs unsigned results

Gregory P. Smith added the comment: binascii and zlib documentation updated in trunk r68535. I'll close the issue after I've merged it into release26-maint, release30-maint and py3k. Any objections to the wording? http://svn.python.org/view/python/trunk/Doc/library/binascii.rst? rev=68535&v

[issue4903] binascii.crc32() - document signed vs unsigned results

Gregory P. Smith added the comment: Agreed, we failed to mention the behavior change in the docs. I'll take care of that. (if its mentioned at all, its mentioned in a note buried in the Misc/NEWS file somewhere) 2to3 could presumably be made to notice crc32 and adler32 calls and warn about