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

2009-01-31 Thread Gregory P. Smith
Gregory P. Smith g...@krypto.org added the comment: wording updated in r69159, thanks. ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4903 ___ ___

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

2009-01-31 Thread Gregory P. Smith
Gregory P. Smith g...@krypto.org added the comment: and r69161, r69160, r69162, r69163, r69164. -- resolution: - fixed status: open - closed versions: +Python 2.7, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4903

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

2009-01-12 Thread Gabriel Genellina
Gabriel Genellina gagsl-...@yahoo.com.ar 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

2009-01-11 Thread Gregory P. Smith
Gregory P. Smith g...@krypto.org 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?

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

2009-01-10 Thread Gregory P. Smith
Gregory P. Smith g...@krypto.org 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