Issue 23354: Loading 2 GiLOC file which raises exception causes wrong traceback (original) (raw)

Created on 2015-01-31 03:40 by SoniEx2, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (5)
msg235079 - (view)	Author: (SoniEx2)	Date: 2015-01-31 03:40
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 AssertionError
msg241196 - (view)	Author: Ethan Furman (ethan.furman) *	Date: 2015-04-16 03:26
Considering how rare (hopefully!) files of that size are, I wouldn't be adverse to a "won't fix" resolution.
msg241197 - (view)	Author: Ethan Furman (ethan.furman) *	Date: 2015-04-16 03:27
Considering how rare (hopefully!) files of that size are, I wouldn't be adverse to a "won't fix" resolution.
msg324932 - (view)	Author: Benjamin Peterson (benjamin.peterson) *	Date: 2018-09-10 16:14
We would need to know what test.py was actually doing to fix this bug.
msg324936 - (view)	Author: (SoniEx2)	Date: 2018-09-10 16:44
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> > _______________________________________ >