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.

classification
Title: repoened "test_maxint64 fails on 32-bit systems due to assumption that 64-bit fits into "long"" due to it being closed without asking me whether there was anything else involved
Type: Stage:
Components: Build Versions: Python 2.5
process
Status: closed Resolution: duplicate
Dependencies: Superseder: test_maxint64 fails on 32-bit systems due to assumption that 64-bit fits into "long"
View: 4977
Assigned To: Nosy List: lkcl, mark.dickinson, pitrou
Priority: normal Keywords:

Created on 2009-01-20 11:12 by lkcl, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (2)
msg80241 - (view) Author: Luke Kenneth Casson Leighton (lkcl) Date: 2009-01-20 11:12
this is reopening http://bugs.python.org/issue4977 because it was closed
without asking whether there was any further information or anything
else that required investigation.

there is no way for me to reopen the bug so i am forced to open a
new one.

mark - don't do that again, please.

the suggestion to use PyOS_strtol was a good one: you should have
left the bug as-is after that suggestion, and WAITED until i had
tested that.

the bug involves 64-bit zip files.

the fact that a 32-bit int is being returned, as -4932893211 (whatever)
instead of 44951 (whatever) is causing the problem.

so will you be kind enough and courteous enough to wait until
i have provided full information and investigated this issue?

or do you not want me to bother?
msg80244 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2009-01-20 11:20
Let's put everything in one place :)
History
Date User Action Args
2022-04-11 14:56:44adminsetgithub: 49260
2009-01-20 11:20:38pitrousetstatus: open -> closed
resolution: duplicate
superseder: test_maxint64 fails on 32-bit systems due to assumption that 64-bit fits into "long"
messages: + msg80244
nosy: + pitrou
2009-01-20 11:12:16lkclcreate