Repository navigation
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 #49260
Description
| BPO | 5010 |
|---|---|
| Nosy | @mdickinson, @pitrou |
| Superseder |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = <Date 2009-01-20.11:20:38.383>
created_at = <Date 2009-01-20.11:12:16.832>
labels = ['build']
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'
updated_at = <Date 2009-01-20.11:20:38.381>
user = 'https://bugs.python.org/lkcl'bugs.python.org fields:
activity = <Date 2009-01-20.11:20:38.381>
actor = 'pitrou'
assignee = 'none'
closed = True
closed_date = <Date 2009-01-20.11:20:38.383>
closer = 'pitrou'
components = ['Build']
creation = <Date 2009-01-20.11:12:16.832>
creator = 'lkcl'
dependencies = []
files = []
hgrepos = []
issue_num = 5010
keywords = []
message_count = 2.0
messages = ['80241', '80244']
nosy_count = 3.0
nosy_names = ['lkcl', 'mark.dickinson', 'pitrou']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = None
status = 'closed'
superseder = '4977'
type = None
url = 'https://bugs.python.org/issue5010'
versions = ['Python 2.5']
Activity
lkcl commentedon Jan 20, 2009
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?
pitrou commentedon Jan 20, 2009
Let's put everything in one place :)