This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | arigo |
|---|---|
| Recipients | arigo |
| Date | 2007年09月25日.11:31:10 |
| SpamBayes Score | 0.32613933 |
| Marked as misclassified | No |
| Message-id | <1190719871.47.0.233788425538.issue1202@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
The functions zlib.crc32() and zlib.adler32() return a signed value in the range(-2147483648, 2147483648) on 32-bit platforms, but an unsigned value in the range(0, 4294967296) on 64-bit platforms. This means that half the possible answers are numerically different on these two kinds of platforms. Ideally, this should be fixed by having them always return unsigned numbers (their C return type is unsigned too). It's unclear if we can do this without breaking existing code, though :-( |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2007年09月25日 11:31:11 | arigo | set | spambayes_score: 0.326139 -> 0.32613933 recipients: + arigo |
| 2007年09月25日 11:31:11 | arigo | set | spambayes_score: 0.326139 -> 0.326139 messageid: <1190719871.47.0.233788425538.issue1202@psf.upfronthosting.co.za> |
| 2007年09月25日 11:31:11 | arigo | link | issue1202 messages |
| 2007年09月25日 11:31:10 | arigo | create | |