Loading 2 GiLOC file which raises exception causes wrong traceback

[SoniEx2]

BPO	23354
Nosy	@vstinner, @benjaminp

^{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 2021-09-03.22:30:34.107>
created_at = <Date 2015-01-31.03:40:41.817>
labels = ['interpreter-core', 'type-bug']
title = 'Loading 2 GiLOC file which raises exception causes wrong traceback'
updated_at = <Date 2021-09-03.22:30:34.107>
user = 'https://bugs.python.org/SoniEx2'

bugs.python.org fields:

activity = <Date 2021-09-03.22:30:34.107>
actor = 'iritkatriel'
assignee = 'none'
closed = True
closed_date = <Date 2021-09-03.22:30:34.107>
closer = 'iritkatriel'
components = ['Interpreter Core']
creation = <Date 2015-01-31.03:40:41.817>
creator = 'SoniEx2'
dependencies = []
files = []
hgrepos = []
issue_num = 23354
keywords = []
message_count = 5.0
messages = ['235079', '241196', '241197', '324932', '324936']
nosy_count = 3.0
nosy_names = ['vstinner', 'benjamin.peterson', 'SoniEx2']
pr_nums = []
priority = 'low'
resolution = 'wont fix'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue23354'
versions = ['Python 3.4']

[SoniEx2]

I loaded a file with 2 GiLOC followed by "assert False" and this was the error/traceback:

Traceback (most recent call last):
  File "test.py", line -2147483647, in <module>
AssertionError

[ethanfurman]

Considering how rare (hopefully!) files of that size are, I wouldn't be adverse to a "won't fix" resolution.

[ethanfurman]

Considering how rare (hopefully!) files of that size are, I wouldn't be adverse to a "won't fix" resolution.

[benjaminp]

We would need to know what test.py was actually doing to fix this bug.

[SoniEx2]

test.py is the result of "\n" * (2**31) + "assert False", written to a
file.

On Mon, Sep 10, 2018, 13:14 Benjamin Peterson <report@bugs.python.org>
wrote:

Benjamin Peterson <benjamin@python.org> added the comment:

We would need to know what test.py was actually doing to fix this bug.

----------
resolution: -> works for me
stage: -> resolved
status: open -> closed

---

Python tracker <report@bugs.python.org>
<https://bugs.python.org/issue23354\>

---