documentation wording fix for issue4903

This commit is contained in:
Gregory P. Smith 2009-02-01 00:30:50 +00:00
parent 548a4cb1f9
commit fa6cf39e70
2 changed files with 6 additions and 6 deletions

View file

@ -120,11 +120,11 @@ The :mod:`binascii` module defines the following functions:
To generate the same numeric value across all Python versions and
platforms use crc32(data) & 0xffffffff. If you are only using
the checksum in packed binary format this is not necessary as the
return value will have the correct 32bit binary representation
return value is the correct 32bit binary representation
regardless of sign.
.. versionchanged:: 3.0
The return value will always be unsigned and in the range [0, 2**32-1]
The return value is unsigned and in the range [0, 2**32-1]
regardless of platform.

View file

@ -48,11 +48,11 @@ The available exception and functions in this module are:
To generate the same numeric value across all Python versions and
platforms use adler32(data) & 0xffffffff. If you are only using
the checksum in packed binary format this is not necessary as the
return value will have the correct 32bit binary representation
return value is the correct 32bit binary representation
regardless of sign.
.. versionchanged:: 3.0
The return value will always be unsigned and in the range [0, 2**32-1]
The return value is unsigned and in the range [0, 2**32-1]
regardless of platform.
@ -93,11 +93,11 @@ The available exception and functions in this module are:
To generate the same numeric value across all Python versions and
platforms use crc32(data) & 0xffffffff. If you are only using
the checksum in packed binary format this is not necessary as the
return value will have the correct 32bit binary representation
return value is the correct 32bit binary representation
regardless of sign.
.. versionchanged:: 3.0
The return value will always be unsigned and in the range [0, 2**32-1]
The return value is unsigned and in the range [0, 2**32-1]
regardless of platform.